Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff2eeb4662e65fe03f96362c04763fbe4a532b92217494eec9683e020814a32

Tx prefix hash: e9b462b1b2d72b5227b42c576724f6eda26771c47bdb288a8fbfca98b92b304a
Tx public key: cf9d822b93db570df968f7fdc74af919e6681f33a48f90e0410c941274d10c46
Timestamp: 1705223280 Timestamp [UCT]: 2024-01-14 09:08:00 Age [y:d:h:m:s]: 01:045:11:20:28
Block: 935037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293561 RingCT/type: yes/0
Extra: 01cf9d822b93db570df968f7fdc74af919e6681f33a48f90e0410c941274d10c46021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54ae2eb91d59e488c949e112260d65b86a21ed8e8c60534c2717bb6a846d5925 0.600000000000 1393053 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": 935047, "vin": [ { "gen": { "height": 935037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54ae2eb91d59e488c949e112260d65b86a21ed8e8c60534c2717bb6a846d5925" } } ], "extra": [ 1, 207, 157, 130, 43, 147, 219, 87, 13, 249, 104, 247, 253, 199, 74, 249, 25, 230, 104, 31, 51, 164, 143, 144, 224, 65, 12, 148, 18, 116, 209, 12, 70, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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