Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e7b95b6502518b70064fe6278b4be09db0ee03b0505a516a2d8a36e1dd7475

Tx prefix hash: 9679409013b8f751ea277671de1f5fe89497281a7d11faf31599a792ace95b14
Tx public key: 020c4b236476be926c358638b5448e25a429b4374e59aa4af9f73171801af7f6
Timestamp: 1720549283 Timestamp [UCT]: 2024-07-09 18:21:23 Age [y:d:h:m:s]: 00:228:09:45:00
Block: 1062117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163130 RingCT/type: yes/0
Extra: 01020c4b236476be926c358638b5448e25a429b4374e59aa4af9f73171801af7f6021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e2dca5e7b516f34711f2672c80a8ae67060d3b65c0fd1f0154820b02b79438 0.600000000000 1532618 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": 1062127, "vin": [ { "gen": { "height": 1062117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e2dca5e7b516f34711f2672c80a8ae67060d3b65c0fd1f0154820b02b79438" } } ], "extra": [ 1, 2, 12, 75, 35, 100, 118, 190, 146, 108, 53, 134, 56, 181, 68, 142, 37, 164, 41, 180, 55, 78, 89, 170, 74, 249, 247, 49, 113, 128, 26, 247, 246, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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