Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e19ef54bde6c3527a10253889db39fc46364ca6d78c4ad4a3a509309ca4ab84f

Tx prefix hash: 2d7211ba383c226df0dbe24120ae7d90818494d9481de568b8a598d08e095133
Tx public key: 2cf73cc063ea82f29db1f3d7f1d2d7bcefd1dd77ad114a162b49e84381ef350b
Timestamp: 1719437054 Timestamp [UCT]: 2024-06-26 21:24:14 Age [y:d:h:m:s]: 01:158:19:59:22
Block: 1052874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372107 RingCT/type: yes/0
Extra: 012cf73cc063ea82f29db1f3d7f1d2d7bcefd1dd77ad114a162b49e84381ef350b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccbf416c9c294f9ab5ac32410b46c8c6e11a5081f53aac8b5c29774d5c191477 0.600000000000 1523209 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": 1052884, "vin": [ { "gen": { "height": 1052874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccbf416c9c294f9ab5ac32410b46c8c6e11a5081f53aac8b5c29774d5c191477" } } ], "extra": [ 1, 44, 247, 60, 192, 99, 234, 130, 242, 157, 177, 243, 215, 241, 210, 215, 188, 239, 209, 221, 119, 173, 17, 74, 22, 43, 73, 232, 67, 129, 239, 53, 11, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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