Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57fc4166798380ddc21226fdb8d7014101985579b7a3b7d2d9f27e377fbcc98

Tx prefix hash: c46b847610a5d32a6526be0f612608e891038c73d9f8a67da30a8665ca7150e4
Tx public key: 06aa51de2b7f5f98d0588c78c67024e9b6396299e7f717ebd020ba9d02a15b90
Timestamp: 1766274220 Timestamp [UCT]: 2025-12-20 23:43:40 Age [y:d:h:m:s]: 00:000:05:44:48
Block: 1438066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163 RingCT/type: yes/0
Extra: 0106aa51de2b7f5f98d0588c78c67024e9b6396299e7f717ebd020ba9d02a15b900211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22e4663589dcc8bf167bd1c96ec8bcccdc28b26ccd0e59d2a4c61c386ae37aa7 0.600000000000 1926881 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": 1438076, "vin": [ { "gen": { "height": 1438066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22e4663589dcc8bf167bd1c96ec8bcccdc28b26ccd0e59d2a4c61c386ae37aa7" } } ], "extra": [ 1, 6, 170, 81, 222, 43, 127, 95, 152, 208, 88, 140, 120, 198, 112, 36, 233, 182, 57, 98, 153, 231, 247, 23, 235, 208, 32, 186, 157, 2, 161, 91, 144, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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