Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0dbd131790c3272cc215170f1b7da655a0159dbdf61cc65b3aab6195afd58c

Tx prefix hash: 717f861c3e47e7b1d3d5dbc823e6a6ce90d847e036e14063b00995234bcf6e13
Tx public key: 1632c134ce020602b1eb56af016ed4555e98b4891bfd4a851306f03f40a7b38e
Timestamp: 1705826508 Timestamp [UCT]: 2024-01-21 08:41:48 Age [y:d:h:m:s]: 01:036:07:49:17
Block: 940015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287039 RingCT/type: yes/0
Extra: 011632c134ce020602b1eb56af016ed4555e98b4891bfd4a851306f03f40a7b38e02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d0a046d68afe227cd9cde592bf2697befd8c51f8bb206fb0d946b1682f15d42 0.600000000000 1398149 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": 940025, "vin": [ { "gen": { "height": 940015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d0a046d68afe227cd9cde592bf2697befd8c51f8bb206fb0d946b1682f15d42" } } ], "extra": [ 1, 22, 50, 193, 52, 206, 2, 6, 2, 177, 235, 86, 175, 1, 110, 212, 85, 94, 152, 180, 137, 27, 253, 74, 133, 19, 6, 240, 63, 64, 167, 179, 142, 2, 17, 0, 0, 0, 11, 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