Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a467af4d35e30036545c5823fbcb32d31ce5b30dd2da069a27b152fc0cf2d54

Tx prefix hash: 90e1b313d7724c7683f543bc428a77db1ed535fd9b9fdf6b751f2173c6b39d76
Tx public key: d00c1a4675b11f859dca78dca143c82bb06c53b504a92311288efe98d238e981
Timestamp: 1703136978 Timestamp [UCT]: 2023-12-21 05:36:18 Age [y:d:h:m:s]: 01:321:16:39:16
Block: 917768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488737 RingCT/type: yes/0
Extra: 01d00c1a4675b11f859dca78dca143c82bb06c53b504a92311288efe98d238e98102110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 296f227287c529c4706e068a02e81797b0c4a32fe99416445ce7988a2a1df9c9 0.600000000000 1375350 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": 917778, "vin": [ { "gen": { "height": 917768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "296f227287c529c4706e068a02e81797b0c4a32fe99416445ce7988a2a1df9c9" } } ], "extra": [ 1, 208, 12, 26, 70, 117, 177, 31, 133, 157, 202, 120, 220, 161, 67, 200, 43, 176, 108, 83, 181, 4, 169, 35, 17, 40, 142, 254, 152, 210, 56, 233, 129, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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