Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce54c2ac307b9588002f076e35a2ecf78db5793e123f8b516f6336fff3f2e863

Tx prefix hash: 3f9e34012ded92c7ebd7e167fd8d9cb3533ea9cbf47c739842e08483a2d72a01
Tx public key: 36ad7b61d7986eba4f3b57da9994ae577a5c05d12ed4a13fb0c01389837ca295
Timestamp: 1747018063 Timestamp [UCT]: 2025-05-12 02:47:43 Age [y:d:h:m:s]: 00:241:13:03:41
Block: 1281011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170414 RingCT/type: yes/0
Extra: 0136ad7b61d7986eba4f3b57da9994ae577a5c05d12ed4a13fb0c01389837ca2950211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4dbf3e95aaffdb26b7f018db6d5d31bbfd6ddabc8781316b8863ac9699ef7b 0.600000000000 1768406 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": 1281021, "vin": [ { "gen": { "height": 1281011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4dbf3e95aaffdb26b7f018db6d5d31bbfd6ddabc8781316b8863ac9699ef7b" } } ], "extra": [ 1, 54, 173, 123, 97, 215, 152, 110, 186, 79, 59, 87, 218, 153, 148, 174, 87, 122, 92, 5, 209, 46, 212, 161, 63, 176, 192, 19, 137, 131, 124, 162, 149, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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