Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c4808773b10b27d31ee65b3bcb81795578cddb0bff1e2d21372940384c46732

Tx prefix hash: d0497f99bc4d5783fb5bfb643c73dcd9b6bd61247382c45bc3c375299cc24e0d
Tx public key: 15ae017435d2ec3263218399b52085a617e78ea1c1a842d8aa618ee8c87ff8b3
Timestamp: 1734244100 Timestamp [UCT]: 2024-12-15 06:28:20 Age [y:d:h:m:s]: 00:133:17:40:12
Block: 1175551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95380 RingCT/type: yes/0
Extra: 0115ae017435d2ec3263218399b52085a617e78ea1c1a842d8aa618ee8c87ff8b30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad0b506e4063ba7fdfdbf19e78426255bff004174c0fdefcaa51f0c51851bc4 0.600000000000 1661846 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": 1175561, "vin": [ { "gen": { "height": 1175551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad0b506e4063ba7fdfdbf19e78426255bff004174c0fdefcaa51f0c51851bc4" } } ], "extra": [ 1, 21, 174, 1, 116, 53, 210, 236, 50, 99, 33, 131, 153, 181, 32, 133, 166, 23, 231, 142, 161, 193, 168, 66, 216, 170, 97, 142, 232, 200, 127, 248, 179, 2, 17, 0, 0, 0, 3, 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