Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a14d2b9333c66988d7ffaca7adccac6564a85a15d72fc228c5a948ce2bbc621

Tx prefix hash: f791297c90048fe8e6cecb27572056820cd60dce869a6550b3c535edb142df65
Tx public key: 8782b9bc209b74fe02986c3b4e2cc867d636d4eefc30a6390c2c5d17f7f69ad2
Timestamp: 1704419438 Timestamp [UCT]: 2024-01-05 01:50:38 Age [y:d:h:m:s]: 01:123:04:28:18
Block: 928363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349182 RingCT/type: yes/0
Extra: 018782b9bc209b74fe02986c3b4e2cc867d636d4eefc30a6390c2c5d17f7f69ad20211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4949d3f49dee26d7829b4a1d020d2c63918097695168c7897173e2ef31cb1a74 0.600000000000 1386221 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": 928373, "vin": [ { "gen": { "height": 928363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4949d3f49dee26d7829b4a1d020d2c63918097695168c7897173e2ef31cb1a74" } } ], "extra": [ 1, 135, 130, 185, 188, 32, 155, 116, 254, 2, 152, 108, 59, 78, 44, 200, 103, 214, 54, 212, 238, 252, 48, 166, 57, 12, 44, 93, 23, 247, 246, 154, 210, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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