Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c582cd52c4c0d1aa8598722734bf20c791114d070b053fda40e139d319ea4eae

Tx prefix hash: 7d96762fe7ae5df86ca0e87fcb78d886f32414642a9dc517b334746e9c00f007
Tx public key: 001cb121f7621c16564d569c45e378f668da5625bdebc8a5b88f8bd092f071de
Timestamp: 1720773897 Timestamp [UCT]: 2024-07-12 08:44:57 Age [y:d:h:m:s]: 00:198:12:21:19
Block: 1063984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141924 RingCT/type: yes/0
Extra: 01001cb121f7621c16564d569c45e378f668da5625bdebc8a5b88f8bd092f071de02110000001791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8186d681cf2a97ebe2f06a9cb92b131261b8063217b2292a85f5ea832efc6f7 0.600000000000 1534505 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": 1063994, "vin": [ { "gen": { "height": 1063984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8186d681cf2a97ebe2f06a9cb92b131261b8063217b2292a85f5ea832efc6f7" } } ], "extra": [ 1, 0, 28, 177, 33, 247, 98, 28, 22, 86, 77, 86, 156, 69, 227, 120, 246, 104, 218, 86, 37, 189, 235, 200, 165, 184, 143, 139, 208, 146, 240, 113, 222, 2, 17, 0, 0, 0, 23, 145, 225, 60, 4, 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