Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16b92ae8a64047684865c898c936a83294fa3263cecb74b3e30f80976ba8249f

Tx prefix hash: 9334e7282c7c76b6408d7bdf1858f3df7a658dc564946856afcdc931cf623086
Tx public key: 1288e402bcc2eff1641fea508ddad2a78d2c5be9cf8803a66db60ee5060fc5dc
Timestamp: 1762601644 Timestamp [UCT]: 2025-11-08 11:34:04 Age [y:d:h:m:s]: 00:013:12:52:37
Block: 1407612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9695 RingCT/type: yes/0
Extra: 011288e402bcc2eff1641fea508ddad2a78d2c5be9cf8803a66db60ee5060fc5dc021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12e8d3abf96e17923e95274ee92159155d3a303e63ce4f9b4c57a8ea272b3cf 0.600000000000 1896033 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": 1407622, "vin": [ { "gen": { "height": 1407612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12e8d3abf96e17923e95274ee92159155d3a303e63ce4f9b4c57a8ea272b3cf" } } ], "extra": [ 1, 18, 136, 228, 2, 188, 194, 239, 241, 100, 31, 234, 80, 141, 218, 210, 167, 141, 44, 91, 233, 207, 136, 3, 166, 109, 182, 14, 229, 6, 15, 197, 220, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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