Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588e3ac7d152d63adaeac79d7c039e2a5552eff3f83d917b1113bc419dc80ccc

Tx prefix hash: 662f4d65106f2a71613b74431879e461bce2dac36f111617e1df5868f4b442a1
Tx public key: f9178f6f2904149ee6e762838304387a10608639f6cff5dac7d90dab7f8d295d
Timestamp: 1697418002 Timestamp [UCT]: 2023-10-16 01:00:02 Age [y:d:h:m:s]: 01:221:01:15:38
Block: 870543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419058 RingCT/type: yes/0
Extra: 01f9178f6f2904149ee6e762838304387a10608639f6cff5dac7d90dab7f8d295d02110000000733af99f4000000000000000000

1 output(s) for total of 0.800810369000 dcy

stealth address amount amount idx
00: e18e4012279e8a9afa44e22f5677d07245409a5b39ed4016fea59b02d3a1d514 0.800810369000 1325424 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": 870553, "vin": [ { "gen": { "height": 870543 } } ], "vout": [ { "amount": 800810369, "target": { "key": "e18e4012279e8a9afa44e22f5677d07245409a5b39ed4016fea59b02d3a1d514" } } ], "extra": [ 1, 249, 23, 143, 111, 41, 4, 20, 158, 230, 231, 98, 131, 131, 4, 56, 122, 16, 96, 134, 57, 246, 207, 245, 218, 199, 217, 13, 171, 127, 141, 41, 93, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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