Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e380d0817e08b511ba4290184de2d5d4372361b70512eafa6e594c945bc38d1

Tx prefix hash: 57d6391f1bc85cb9b2551cc20c393abed743b2a6edfb4df9c2420edc0c31b6c8
Tx public key: 9e360f59c96f70bcfbbdb063238e0ab2ced980e583f5a2a1c1f89ae6c3429666
Timestamp: 1582984830 Timestamp [UCT]: 2020-02-29 14:00:30 Age [y:d:h:m:s]: 04:250:19:29:56
Block: 74150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1072846 RingCT/type: yes/0
Extra: 019e360f59c96f70bcfbbdb063238e0ab2ced980e583f5a2a1c1f89ae6c342966602110000025f0aca7173000000000000000000

1 output(s) for total of 348.598294193000 dcy

stealth address amount amount idx
00: fa0dfe4a79261237cd3a98b8ca825cb9bdd037eff79b3deac8f046b1d0437bc1 348.598294193000 137071 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": 74160, "vin": [ { "gen": { "height": 74150 } } ], "vout": [ { "amount": 348598294193, "target": { "key": "fa0dfe4a79261237cd3a98b8ca825cb9bdd037eff79b3deac8f046b1d0437bc1" } } ], "extra": [ 1, 158, 54, 15, 89, 201, 111, 112, 188, 251, 189, 176, 99, 35, 142, 10, 178, 206, 217, 128, 229, 131, 245, 162, 161, 193, 248, 154, 230, 195, 66, 150, 102, 2, 17, 0, 0, 2, 95, 10, 202, 113, 115, 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