Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 139546522a2a9eba3bd5f97dda17cf61de3c2d3a2d43565ae52f9f4ed1e9d0dc

Tx prefix hash: 2d1da0c824e86096fb3f3bcc7e119ad2bc7c4707085e60e6cc2e9100399455da
Tx public key: 5e93ef1fadc7a24515eb89e537e9fb5d58bd37cff7192ce018fb153a8feca149
Timestamp: 1728701003 Timestamp [UCT]: 2024-10-12 02:43:23 Age [y:d:h:m:s]: 00:185:09:15:19
Block: 1129706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132268 RingCT/type: yes/0
Extra: 015e93ef1fadc7a24515eb89e537e9fb5d58bd37cff7192ce018fb153a8feca1490211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e67223820221d9141eb4a1b95dcebd4ecebf2cedf9de21f9c1534dc85a8d305d 0.600000000000 1612549 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": 1129716, "vin": [ { "gen": { "height": 1129706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e67223820221d9141eb4a1b95dcebd4ecebf2cedf9de21f9c1534dc85a8d305d" } } ], "extra": [ 1, 94, 147, 239, 31, 173, 199, 162, 69, 21, 235, 137, 229, 55, 233, 251, 93, 88, 189, 55, 207, 247, 25, 44, 224, 24, 251, 21, 58, 143, 236, 161, 73, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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