Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b825c83ac93b6f0e1207c6e4e5092c287783878ea591914a7ebd163b97eba7

Tx prefix hash: 897631c818ab18cbcf8d4315012074b150324656b2315503709b7591d78af532
Tx public key: 9d581c1e28090c11ef0f11c322d7f7ac8584ebb196fd69d25ea5d04b83c75b3e
Timestamp: 1707102614 Timestamp [UCT]: 2024-02-05 03:10:14 Age [y:d:h:m:s]: 01:071:15:05:06
Block: 950613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312262 RingCT/type: yes/0
Extra: 019d581c1e28090c11ef0f11c322d7f7ac8584ebb196fd69d25ea5d04b83c75b3e0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3110ba639587806776a38a08019bfe0cf72286d1a1c36028c5920b396c3ee5e1 0.600000000000 1409259 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": 950623, "vin": [ { "gen": { "height": 950613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3110ba639587806776a38a08019bfe0cf72286d1a1c36028c5920b396c3ee5e1" } } ], "extra": [ 1, 157, 88, 28, 30, 40, 9, 12, 17, 239, 15, 17, 195, 34, 215, 247, 172, 133, 132, 235, 177, 150, 253, 105, 210, 94, 165, 208, 75, 131, 199, 91, 62, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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