Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd15f6cf175c305c827f441d142ca4b88efab41fbf9c18605007b41c49dd2583

Tx prefix hash: 05049b110e60bcb6a339dcd69dd4479ca2a9168a508f25e53a9174b7ba2d6191
Tx public key: cd3a187678a80b76f775668d551048e51ff9c2ae9445f42c3d7d10e311d3dbe4
Timestamp: 1727141353 Timestamp [UCT]: 2024-09-24 01:29:13 Age [y:d:h:m:s]: 00:198:19:59:33
Block: 1116760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141923 RingCT/type: yes/0
Extra: 01cd3a187678a80b76f775668d551048e51ff9c2ae9445f42c3d7d10e311d3dbe402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7912776da364c5c8bbb95b9c6776f4e8de84c56687c9b9c7b8fc9a3ac7e3a740 0.600000000000 1597357 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": 1116770, "vin": [ { "gen": { "height": 1116760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7912776da364c5c8bbb95b9c6776f4e8de84c56687c9b9c7b8fc9a3ac7e3a740" } } ], "extra": [ 1, 205, 58, 24, 118, 120, 168, 11, 118, 247, 117, 102, 141, 85, 16, 72, 229, 31, 249, 194, 174, 148, 69, 244, 44, 61, 125, 16, 227, 17, 211, 219, 228, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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