Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93de617c96785245e38d2cce89d8887561d4ceafc3703766d7456cee6675267a

Tx prefix hash: e83267fcc10e3c6e47995d66492df62b67563987579313c8ed345d75019675a5
Tx public key: dc3603df07d72e092bbaa4b0a4296d8dcf9f6cc9e1921a79f6ae108e336162d1
Timestamp: 1580977765 Timestamp [UCT]: 2020-02-06 08:29:25 Age [y:d:h:m:s]: 05:028:00:49:05
Block: 59742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172119 RingCT/type: yes/0
Extra: 01dc3603df07d72e092bbaa4b0a4296d8dcf9f6cc9e1921a79f6ae108e336162d10211000000027adf42d3000000000000000000

1 output(s) for total of 389.109790255000 dcy

stealth address amount amount idx
00: a8c38f634ee4b758455cba6e75407c8283c2ad8f15a50b7d44652081bfb07471 389.109790255000 110238 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": 59752, "vin": [ { "gen": { "height": 59742 } } ], "vout": [ { "amount": 389109790255, "target": { "key": "a8c38f634ee4b758455cba6e75407c8283c2ad8f15a50b7d44652081bfb07471" } } ], "extra": [ 1, 220, 54, 3, 223, 7, 215, 46, 9, 43, 186, 164, 176, 164, 41, 109, 141, 207, 159, 108, 201, 225, 146, 26, 121, 246, 174, 16, 142, 51, 97, 98, 209, 2, 17, 0, 0, 0, 2, 122, 223, 66, 211, 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