Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccd3962333348160a5902bd671a395a96dee177f9940e8af77377477c3297a30

Tx prefix hash: 67019a9966cb1be124d1955fa097ca7c50d12b3df1c9e0430f4385fd636a148f
Tx public key: b8723831377908ebc36bdd0d469598e3e2ff8c8bff6d257e636f85e48b3fd3f9
Timestamp: 1718302642 Timestamp [UCT]: 2024-06-13 18:17:22 Age [y:d:h:m:s]: 00:224:17:10:17
Block: 1043480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160770 RingCT/type: yes/0
Extra: 01b8723831377908ebc36bdd0d469598e3e2ff8c8bff6d257e636f85e48b3fd3f90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e36860c9f7df2db3a200ffddb7b8062acbd92b36a85d02dc32f940b06ae2215 0.600000000000 1512633 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": 1043490, "vin": [ { "gen": { "height": 1043480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e36860c9f7df2db3a200ffddb7b8062acbd92b36a85d02dc32f940b06ae2215" } } ], "extra": [ 1, 184, 114, 56, 49, 55, 121, 8, 235, 195, 107, 221, 13, 70, 149, 152, 227, 226, 255, 140, 139, 255, 109, 37, 126, 99, 111, 133, 228, 139, 63, 211, 249, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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