Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c06b3fb012ddab8dbde0b62f391408b38686f1402e9c6c436ee455c2e706a06

Tx prefix hash: 12dafd804d14bbc652fe8ca7ed9661499e9795c5e979aa65af7ded5a280f7887
Tx public key: a371cc56bcd1e537f1a53e75a1a3497e241606827e63197ea2209d99c8680dd0
Timestamp: 1713392426 Timestamp [UCT]: 2024-04-17 22:20:26 Age [y:d:h:m:s]: 00:362:01:02:58
Block: 1002760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258833 RingCT/type: yes/0
Extra: 01a371cc56bcd1e537f1a53e75a1a3497e241606827e63197ea2209d99c8680dd002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 206e282fb3c0f215fe96ad292f26f679d42ef455f2e416846bb9f6f9aee164b8 0.600000000000 1463282 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": 1002770, "vin": [ { "gen": { "height": 1002760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "206e282fb3c0f215fe96ad292f26f679d42ef455f2e416846bb9f6f9aee164b8" } } ], "extra": [ 1, 163, 113, 204, 86, 188, 209, 229, 55, 241, 165, 62, 117, 161, 163, 73, 126, 36, 22, 6, 130, 126, 99, 25, 126, 162, 32, 157, 153, 200, 104, 13, 208, 2, 17, 0, 0, 0, 3, 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