Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55ea5e2cfb81d9366f3ca51ebcbab5ea7070e4d39ae398af67ffc14650c8b3c2

Tx prefix hash: 3290af35a93dc76f70e314528d720cdafa3d12cc2515797688b1452b91bfddb1
Tx public key: 00a6a9df31b2ef60f59c4acd1e47b2838a68b2ee2d73ac117f2368c132defbac
Timestamp: 1736513842 Timestamp [UCT]: 2025-01-10 12:57:22 Age [y:d:h:m:s]: 00:159:10:47:55
Block: 1194322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113653 RingCT/type: yes/0
Extra: 0100a6a9df31b2ef60f59c4acd1e47b2838a68b2ee2d73ac117f2368c132defbac0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f967ebc2cce2c140e78a13a88fdf89ec95edb9cc0c73c9e0646fdd0366e63959 0.600000000000 1680891 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": 1194332, "vin": [ { "gen": { "height": 1194322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f967ebc2cce2c140e78a13a88fdf89ec95edb9cc0c73c9e0646fdd0366e63959" } } ], "extra": [ 1, 0, 166, 169, 223, 49, 178, 239, 96, 245, 156, 74, 205, 30, 71, 178, 131, 138, 104, 178, 238, 45, 115, 172, 17, 127, 35, 104, 193, 50, 222, 251, 172, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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