Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e38a2ef1a49fe86c87993635c3c92c17cfe3161a675a4c461bb80f5fcaeb286

Tx prefix hash: aac8ac3022f20377bf5341d607ece36da6bb6c119eba19c948af7571d5c8a624
Tx public key: 4143c011d023828fdcccf93a9e1555ddd0ba2f7dc7c0d04d4066344111c6a1b5
Timestamp: 1742779057 Timestamp [UCT]: 2025-03-24 01:17:37 Age [y:d:h:m:s]: 00:312:20:51:51
Block: 1245914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221262 RingCT/type: yes/0
Extra: 014143c011d023828fdcccf93a9e1555ddd0ba2f7dc7c0d04d4066344111c6a1b5021100000002c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c64e35b2c1005086d4dd525921e5459330c292884cf03e90a79e76d8b5f30e 0.600000000000 1732909 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": 1245924, "vin": [ { "gen": { "height": 1245914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c64e35b2c1005086d4dd525921e5459330c292884cf03e90a79e76d8b5f30e" } } ], "extra": [ 1, 65, 67, 192, 17, 208, 35, 130, 143, 220, 204, 249, 58, 158, 21, 85, 221, 208, 186, 47, 125, 199, 192, 208, 77, 64, 102, 52, 65, 17, 198, 161, 181, 2, 17, 0, 0, 0, 2, 198, 116, 9, 88, 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