Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22bf2cf1a92e2868d5a9fceb8c39b82e5e549d611455f213310449c6ef5a08f8

Tx prefix hash: 412b51ce4892c5046fa0b4d31085a9acfeea9d29db26accd0c686185c5cc2c94
Tx public key: 71028aaafc0d16105e5d38c62805df98d6f26a45e9e71a9c1eee82f87f022d86
Timestamp: 1588735816 Timestamp [UCT]: 2020-05-06 03:30:16 Age [y:d:h:m:s]: 05:157:00:22:25
Block: 98873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1287036 RingCT/type: yes/0
Extra: 0171028aaafc0d16105e5d38c62805df98d6f26a45e9e71a9c1eee82f87f022d860211000000ef39be35fb000000000000000000

1 output(s) for total of 288.664561717000 dcy

stealth address amount amount idx
00: b158c277d629777e2c0d6350d1c44e6cecce65dfe165a4f8f75ce0a973c023b3 288.664561717000 174665 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": 98883, "vin": [ { "gen": { "height": 98873 } } ], "vout": [ { "amount": 288664561717, "target": { "key": "b158c277d629777e2c0d6350d1c44e6cecce65dfe165a4f8f75ce0a973c023b3" } } ], "extra": [ 1, 113, 2, 138, 170, 252, 13, 22, 16, 94, 93, 56, 198, 40, 5, 223, 152, 214, 242, 106, 69, 233, 231, 26, 156, 30, 238, 130, 248, 127, 2, 45, 134, 2, 17, 0, 0, 0, 239, 57, 190, 53, 251, 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