Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954ed0a5875814bd9d32d70a3b44a1c6b91ed3942b745f0722a965e49bae6619

Tx prefix hash: d5d98f0c2fddccbf0fb3a75fa419117057a6e89f91411292858bd7e5df5680a2
Tx public key: ac211773ce27cacd08667c8221f0010abf494773f4e51b854d0948db1f4235e7
Timestamp: 1709987372 Timestamp [UCT]: 2024-03-09 12:29:32 Age [y:d:h:m:s]: 00:351:04:34:23
Block: 974555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251078 RingCT/type: yes/0
Extra: 01ac211773ce27cacd08667c8221f0010abf494773f4e51b854d0948db1f4235e702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c64d4f13415cf9c0c13e85e6ce2dfa4027c78a311c474583e5ef4a7df9b86db7 0.600000000000 1434514 of 15

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": 974565, "vin": [ { "gen": { "height": 974555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c64d4f13415cf9c0c13e85e6ce2dfa4027c78a311c474583e5ef4a7df9b86db7" } } ], "extra": [ 1, 172, 33, 23, 115, 206, 39, 202, 205, 8, 102, 124, 130, 33, 240, 1, 10, 191, 73, 71, 115, 244, 229, 27, 133, 77, 9, 72, 219, 31, 66, 53, 231, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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