Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d12e7647a80a4d025d9a9455d338d0712705036be9ef25ba75357193f6c543

Tx prefix hash: 27ce8cc83d8c9c2bf6c03c626397cfa0074e35d6861682c83ae4d1a6d719ae57
Tx public key: dc3bfe416ee015d154c536e51ab1f4bd45f6dc513d4c36e6cf57ed384bb35f29
Timestamp: 1712072707 Timestamp [UCT]: 2024-04-02 15:45:07 Age [y:d:h:m:s]: 01:217:14:10:32
Block: 991803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414209 RingCT/type: yes/0
Extra: 01dc3bfe416ee015d154c536e51ab1f4bd45f6dc513d4c36e6cf57ed384bb35f290211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7988a416ea53286bcd719fdd911059230dd222d20378ae48495b89da1b1c47d 0.600000000000 1452139 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": 991813, "vin": [ { "gen": { "height": 991803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7988a416ea53286bcd719fdd911059230dd222d20378ae48495b89da1b1c47d" } } ], "extra": [ 1, 220, 59, 254, 65, 110, 224, 21, 209, 84, 197, 54, 229, 26, 177, 244, 189, 69, 246, 220, 81, 61, 76, 54, 230, 207, 87, 237, 56, 75, 179, 95, 41, 2, 17, 0, 0, 0, 4, 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