Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a369d9eb90836e779ac7145d713ab26c5916838205ed8c1f2f7ee25b333ee075

Tx prefix hash: ebc197b647215fd4d3f7893918c89b6ff4a3a7969ed84260b414585af0686842
Tx public key: c36a08765fdaa4c6f2d0da9a413659e96dac8a0cc7ab9e9aff56cb5c4b98ac8c
Timestamp: 1705792750 Timestamp [UCT]: 2024-01-20 23:19:10 Age [y:d:h:m:s]: 01:116:15:18:40
Block: 939738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344494 RingCT/type: yes/0
Extra: 01c36a08765fdaa4c6f2d0da9a413659e96dac8a0cc7ab9e9aff56cb5c4b98ac8c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd92bfd549bec429cb00ed3fd146bb7d2630fa8638b7cebc6245a88c0eb5bba9 0.600000000000 1397854 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": 939748, "vin": [ { "gen": { "height": 939738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd92bfd549bec429cb00ed3fd146bb7d2630fa8638b7cebc6245a88c0eb5bba9" } } ], "extra": [ 1, 195, 106, 8, 118, 95, 218, 164, 198, 242, 208, 218, 154, 65, 54, 89, 233, 109, 172, 138, 12, 199, 171, 158, 154, 255, 86, 203, 92, 75, 152, 172, 140, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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