Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029ac965672cfbf50ff51e394db6003ad87aace9fb6d77b4c183760c4764410e

Tx prefix hash: 96eaa851d13b3f5d3590870a6a014227cf2cf5a0a43b9ce40e9711a5bed15450
Tx public key: b808e1fa0958d23727a30b3a36056d31a77c5fd8360271a1fd2048363fa76a26
Timestamp: 1696041956 Timestamp [UCT]: 2023-09-30 02:45:56 Age [y:d:h:m:s]: 01:047:17:45:03
Block: 859131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295347 RingCT/type: yes/0
Extra: 01b808e1fa0958d23727a30b3a36056d31a77c5fd8360271a1fd2048363fa76a26021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.873659891000 dcy

stealth address amount amount idx
00: f4e4af99e2d56261d43b6f1cc724722351b3d8d24ba544479f12340ece1d44e8 0.873659891000 1313341 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": 859141, "vin": [ { "gen": { "height": 859131 } } ], "vout": [ { "amount": 873659891, "target": { "key": "f4e4af99e2d56261d43b6f1cc724722351b3d8d24ba544479f12340ece1d44e8" } } ], "extra": [ 1, 184, 8, 225, 250, 9, 88, 210, 55, 39, 163, 11, 58, 54, 5, 109, 49, 167, 124, 95, 216, 54, 2, 113, 161, 253, 32, 72, 54, 63, 167, 106, 38, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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