Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2214baf6698f13ecfaf2ceb2117bcaafbaafae4685c4c668a9c842547fab496

Tx prefix hash: d56bf06929321bf069900f6699953b8f2363ce9e0a2b8b51652079fd7a36e646
Tx public key: 363d36033ee7f0d39bc3b85f0ab3fc24f33a6237f16d10f988d5a7fc1f1249c2
Timestamp: 1672554260 Timestamp [UCT]: 2023-01-01 06:24:20 Age [y:d:h:m:s]: 02:162:14:22:16
Block: 665071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 637927 RingCT/type: yes/0
Extra: 01363d36033ee7f0d39bc3b85f0ab3fc24f33a6237f16d10f988d5a7fc1f1249c202110000000352542ceb000000000000000000

1 output(s) for total of 3.840109933000 dcy

stealth address amount amount idx
00: 8b116df13ecc1c6d2aa573e3bbe75fb79dea15964d43243344c63014e5dd774c 3.840109933000 1106086 of 0

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": 665081, "vin": [ { "gen": { "height": 665071 } } ], "vout": [ { "amount": 3840109933, "target": { "key": "8b116df13ecc1c6d2aa573e3bbe75fb79dea15964d43243344c63014e5dd774c" } } ], "extra": [ 1, 54, 61, 54, 3, 62, 231, 240, 211, 155, 195, 184, 95, 10, 179, 252, 36, 243, 58, 98, 55, 241, 109, 16, 249, 136, 213, 167, 252, 31, 18, 73, 194, 2, 17, 0, 0, 0, 3, 82, 84, 44, 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