Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03821b6862aee14a904749b8aeb6598573404af4568c9f612e2000e821273d91

Tx prefix hash: 28215704fadee5ebae836f6b258a53c47504faf8d21c0acc1b1ec5bc793063ee
Tx public key: b124ba2bd853e2c34a3acbf155b9566de3f906dc0c0e4c844f6c2d8604af5eed
Timestamp: 1702263173 Timestamp [UCT]: 2023-12-11 02:52:53 Age [y:d:h:m:s]: 01:188:01:07:12
Block: 910504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395489 RingCT/type: yes/0
Extra: 01b124ba2bd853e2c34a3acbf155b9566de3f906dc0c0e4c844f6c2d8604af5eed0211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f11887739e612a5f8e7608617b3a14efca0bca74ef2cbf99a077166a92692de 0.600000000000 1367665 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": 910514, "vin": [ { "gen": { "height": 910504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f11887739e612a5f8e7608617b3a14efca0bca74ef2cbf99a077166a92692de" } } ], "extra": [ 1, 177, 36, 186, 43, 216, 83, 226, 195, 74, 58, 203, 241, 85, 185, 86, 109, 227, 249, 6, 220, 12, 14, 76, 132, 79, 108, 45, 134, 4, 175, 94, 237, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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