Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5484b42286813871d04c210675de3d80c26b3942bf4a2452849b579d1d227bde

Tx prefix hash: 8fef44d9b205653349ff92b2ffe15ad021e7ef86ff80a96e5c9a8bec109c483a
Tx public key: aff906e58751f820fa25ab25a0cae810f8ebca3bca3c1b226d5adc7d757c15c3
Timestamp: 1584980050 Timestamp [UCT]: 2020-03-23 16:14:10 Age [y:d:h:m:s]: 05:038:00:17:23
Block: 87204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184934 RingCT/type: yes/0
Extra: 01aff906e58751f820fa25ab25a0cae810f8ebca3bca3c1b226d5adc7d757c15c302110000001c8a2ee0d9000000000000000000

1 output(s) for total of 315.542402076000 dcy

stealth address amount amount idx
00: ad459451e687071f5ee368d0b46083fabfcc236c9da2b651a4ffabe44fa38343 315.542402076000 157262 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": 87214, "vin": [ { "gen": { "height": 87204 } } ], "vout": [ { "amount": 315542402076, "target": { "key": "ad459451e687071f5ee368d0b46083fabfcc236c9da2b651a4ffabe44fa38343" } } ], "extra": [ 1, 175, 249, 6, 229, 135, 81, 248, 32, 250, 37, 171, 37, 160, 202, 232, 16, 248, 235, 202, 59, 202, 60, 27, 34, 109, 90, 220, 125, 117, 124, 21, 195, 2, 17, 0, 0, 0, 28, 138, 46, 224, 217, 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