Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c65e0c8fbfbaa6535a3f047dc172589afb74ef811dee1f4055e7d86fac3df61

Tx prefix hash: 94d64a859d982feee1dcd01bd9202787c27f7c625c5da9f7d522ee5b109eaa3d
Tx public key: 2fded4ec88ce48ae45c44df85025e16377a7edb57e19ebf77cd92e4cbb2438e3
Timestamp: 1760873369 Timestamp [UCT]: 2025-10-19 11:29:29 Age [y:d:h:m:s]: 00:071:05:45:23
Block: 1393315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50990 RingCT/type: yes/0
Extra: 012fded4ec88ce48ae45c44df85025e16377a7edb57e19ebf77cd92e4cbb2438e3021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afe41727def6456ee8ce892b59086ba8525465928bc5e2df04ca108b7418fd5b 0.600000000000 1881578 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": 1393325, "vin": [ { "gen": { "height": 1393315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe41727def6456ee8ce892b59086ba8525465928bc5e2df04ca108b7418fd5b" } } ], "extra": [ 1, 47, 222, 212, 236, 136, 206, 72, 174, 69, 196, 77, 248, 80, 37, 225, 99, 119, 167, 237, 181, 126, 25, 235, 247, 124, 217, 46, 76, 187, 36, 56, 227, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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