Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f33607b0ce212c24bbfb83e3d03a0f40212a6b3b103965138f44ea6612d28401

Tx prefix hash: 068111aea481dded6d803fddf6056b779b7c8d24980ec2efd0a1958735d3e07a
Tx public key: 1a239a00fa476ef1f832406c5d5178b714778f757e26432ea6a29c923d81719f
Timestamp: 1732678691 Timestamp [UCT]: 2024-11-27 03:38:11 Age [y:d:h:m:s]: 00:343:18:06:02
Block: 1162562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243201 RingCT/type: yes/0
Extra: 011a239a00fa476ef1f832406c5d5178b714778f757e26432ea6a29c923d81719f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6d2fe903449ee5eac1647a20edf04e4fc66d09470c56e242d5b2fcd48ea9f75 0.600000000000 1648219 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": 1162572, "vin": [ { "gen": { "height": 1162562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6d2fe903449ee5eac1647a20edf04e4fc66d09470c56e242d5b2fcd48ea9f75" } } ], "extra": [ 1, 26, 35, 154, 0, 250, 71, 110, 241, 248, 50, 64, 108, 93, 81, 120, 183, 20, 119, 143, 117, 126, 38, 67, 46, 166, 162, 156, 146, 61, 129, 113, 159, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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