Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 80d8d3d406bf28d8a9b0415226ae54eddaac50a5fb3e5879f1d52c1aa72adda5

Tx prefix hash: 884f6894d30253ec022d6da9c94d2a64a138a2d3ee40ef051679ac19e6d57349
Tx public key: f7f0c2f3708ee6be23415c46c950b3a62ec2264b47c9798b475c17ba44f3a903
Timestamp: 1695626565 Timestamp [UCT]: 2023-09-25 07:22:45 Age [y:d:h:m:s]: 01:128:15:24:11
Block: 855686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352968 RingCT/type: yes/0
Extra: 01f7f0c2f3708ee6be23415c46c950b3a62ec2264b47c9798b475c17ba44f3a90302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.896927042000 dcy

stealth address amount amount idx
00: 13daec619b8eb09a0f7f69c45d6fe587a25c7df3cd398b740ba34d99181e28cf 0.896927042000 1309722 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 855696, "vin": [ { "gen": { "height": 855686 } } ], "vout": [ { "amount": 896927042, "target": { "key": "13daec619b8eb09a0f7f69c45d6fe587a25c7df3cd398b740ba34d99181e28cf" } } ], "extra": [ 1, 247, 240, 194, 243, 112, 142, 230, 190, 35, 65, 92, 70, 201, 80, 179, 166, 46, 194, 38, 75, 71, 201, 121, 139, 71, 92, 23, 186, 68, 243, 169, 3, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8