Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca714a3b487256b7e0e4f0dc963a2f7701a46a3798e25754ce08b3506d503090

Tx prefix hash: 25efda290165eda60385767de18cad2884e7decd794f5d4638b0c8ccd190958e
Tx public key: 058df06e13cb3cd923b815d8f2b226e38594dceaaf30138567db1697ea8d19dd
Timestamp: 1716107814 Timestamp [UCT]: 2024-05-19 08:36:54 Age [y:d:h:m:s]: 00:248:17:48:45
Block: 1025296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177966 RingCT/type: yes/0
Extra: 01058df06e13cb3cd923b815d8f2b226e38594dceaaf30138567db1697ea8d19dd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3afe97b8072a1b48e962f3309fce0c98a9d5b12e65dc76ca677881fd8f460bd 0.600000000000 1491697 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": 1025306, "vin": [ { "gen": { "height": 1025296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3afe97b8072a1b48e962f3309fce0c98a9d5b12e65dc76ca677881fd8f460bd" } } ], "extra": [ 1, 5, 141, 240, 110, 19, 203, 60, 217, 35, 184, 21, 216, 242, 178, 38, 227, 133, 148, 220, 234, 175, 48, 19, 133, 103, 219, 22, 151, 234, 141, 25, 221, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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