Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d1f6d7a37a7054d05a5dc22d1c16e600b44c6fa625594d45347127eaf384c38

Tx prefix hash: e4d4fba88f1bdfb8745c5a5fc44d431000209a63ac96269a539eb20cbb62c4c8
Tx public key: e6c9124ac140638a98c99fa048962be5d4e9e5f7a2ba51992f7a60a22f352804
Timestamp: 1714989172 Timestamp [UCT]: 2024-05-06 09:52:52 Age [y:d:h:m:s]: 00:334:10:28:58
Block: 1016011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239056 RingCT/type: yes/0
Extra: 01e6c9124ac140638a98c99fa048962be5d4e9e5f7a2ba51992f7a60a22f35280402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ba44d918a39308a8b78171dd80b916581a7947e91ea6951dba26780b520e9e 0.600000000000 1479474 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": 1016021, "vin": [ { "gen": { "height": 1016011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ba44d918a39308a8b78171dd80b916581a7947e91ea6951dba26780b520e9e" } } ], "extra": [ 1, 230, 201, 18, 74, 193, 64, 99, 138, 152, 201, 159, 160, 72, 150, 43, 229, 212, 233, 229, 247, 162, 186, 81, 153, 47, 122, 96, 162, 47, 53, 40, 4, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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