Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e04b5f4d7ef28496640cfa5e10094f661f9348f2896fcb4c113cc138648a82f

Tx prefix hash: 4650dcd158d9dd1e7e77435444e2f774787c32b5b3e86066bfab2dcc09b46129
Tx public key: 5288a8eb0bea6ad66ae5c15a95c557752d0b4c3195e727e54015486e990f6576
Timestamp: 1744159890 Timestamp [UCT]: 2025-04-09 00:51:30 Age [y:d:h:m:s]: 00:225:01:23:54
Block: 1257352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158585 RingCT/type: yes/0
Extra: 015288a8eb0bea6ad66ae5c15a95c557752d0b4c3195e727e54015486e990f65760211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 824ac34cf63585a53dfb3105d1f4daf7c47343937401f3df0bb43543e4276335 0.600000000000 1744473 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": 1257362, "vin": [ { "gen": { "height": 1257352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "824ac34cf63585a53dfb3105d1f4daf7c47343937401f3df0bb43543e4276335" } } ], "extra": [ 1, 82, 136, 168, 235, 11, 234, 106, 214, 106, 229, 193, 90, 149, 197, 87, 117, 45, 11, 76, 49, 149, 231, 39, 229, 64, 21, 72, 110, 153, 15, 101, 118, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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