Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5060c081a0c39467f0f0271c2ac6b98d139b8249f269f8343c0c36d22e5d2eec

Tx prefix hash: 63d127cefeae06cdbd2b08cb6758f8ed70ca63d9b1b119ae07ce860a8b628439
Tx public key: 8a00e67210c636b606c80c24a691c80dd390324314f082dfe614e668232dcebf
Timestamp: 1708490842 Timestamp [UCT]: 2024-02-21 04:47:22 Age [y:d:h:m:s]: 01:069:12:08:58
Block: 962132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310716 RingCT/type: yes/0
Extra: 018a00e67210c636b606c80c24a691c80dd390324314f082dfe614e668232dcebf02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31b8c9877440d4e07c9e9d8c5827ec3b871778ac7d3bed2d156f962d7ba7df9 0.600000000000 1421755 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": 962142, "vin": [ { "gen": { "height": 962132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31b8c9877440d4e07c9e9d8c5827ec3b871778ac7d3bed2d156f962d7ba7df9" } } ], "extra": [ 1, 138, 0, 230, 114, 16, 198, 54, 182, 6, 200, 12, 36, 166, 145, 200, 13, 211, 144, 50, 67, 20, 240, 130, 223, 230, 20, 230, 104, 35, 45, 206, 191, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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