Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23a8dfbfea51bc157f4539fb3cd13bcc794cf7a1a4e6a53293ee80452283ec23

Tx prefix hash: 548ddce64951057a9ac20261f19d303baaa128087c0ba2a648fa2ff5651ca6a5
Tx public key: 3efb7617044ff407ad6bbed65dd7372d1217d5e9a9bced1dfc6a1ee1ff56f5ab
Timestamp: 1745226295 Timestamp [UCT]: 2025-04-21 09:04:55 Age [y:d:h:m:s]: 00:256:04:36:42
Block: 1266170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180904 RingCT/type: yes/0
Extra: 013efb7617044ff407ad6bbed65dd7372d1217d5e9a9bced1dfc6a1ee1ff56f5ab0211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e58cb1e7c69b2d5405cfddd87474ae1395141e467b3319bac9a66cf4377d61e 0.600000000000 1753387 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": 1266180, "vin": [ { "gen": { "height": 1266170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e58cb1e7c69b2d5405cfddd87474ae1395141e467b3319bac9a66cf4377d61e" } } ], "extra": [ 1, 62, 251, 118, 23, 4, 79, 244, 7, 173, 107, 190, 214, 93, 215, 55, 45, 18, 23, 213, 233, 169, 188, 237, 29, 252, 106, 30, 225, 255, 86, 245, 171, 2, 17, 0, 0, 0, 6, 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