Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 943b3317416f1cef9d5ee01bcd0a095fa513a68611a024d036fd8d420c9070db

Tx prefix hash: e49c87316df0fbb3d866d7dfe4d77d380a1fe2a4c07a0b99ebc7171e14d3e812
Tx public key: 8f3c07eecaa570945ad1b9f647f31d152b51cf1a0fd89eba6b4d5c45dc089e54
Timestamp: 1736779129 Timestamp [UCT]: 2025-01-13 14:38:49 Age [y:d:h:m:s]: 00:064:20:12:01
Block: 1196519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46136 RingCT/type: yes/0
Extra: 018f3c07eecaa570945ad1b9f647f31d152b51cf1a0fd89eba6b4d5c45dc089e5402110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c405f2945140276be8bc367e615b00b097e4eaf2e2648ada63c9ca06a8d5c9 0.600000000000 1683118 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": 1196529, "vin": [ { "gen": { "height": 1196519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c405f2945140276be8bc367e615b00b097e4eaf2e2648ada63c9ca06a8d5c9" } } ], "extra": [ 1, 143, 60, 7, 238, 202, 165, 112, 148, 90, 209, 185, 246, 71, 243, 29, 21, 43, 81, 207, 26, 15, 216, 158, 186, 107, 77, 92, 69, 220, 8, 158, 84, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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