Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23089b198b69b48ba3356a009f60d5f3abc56b38be12549cbb1e578b2c71da01

Tx prefix hash: 9da1c645006e333cffce4b8b8fbb0ca626ef87f81aeb6ac50a724b135ff3f7d2
Tx public key: 268a2f3b19829a2867973277780f0bf275e8d8added606547e1c73c8ed7a61bc
Timestamp: 1584525542 Timestamp [UCT]: 2020-03-18 09:59:02 Age [y:d:h:m:s]: 04:325:07:55:41
Block: 84887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127917 RingCT/type: yes/0
Extra: 01268a2f3b19829a2867973277780f0bf275e8d8added606547e1c73c8ed7a61bc0211000000014943cd9f000000000000000000

1 output(s) for total of 321.169956960000 dcy

stealth address amount amount idx
00: 4f72511691b0549dcf0caa8c207e0d38805e032a4cd6a374f6cf34dad671fce3 321.169956960000 153657 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": 84897, "vin": [ { "gen": { "height": 84887 } } ], "vout": [ { "amount": 321169956960, "target": { "key": "4f72511691b0549dcf0caa8c207e0d38805e032a4cd6a374f6cf34dad671fce3" } } ], "extra": [ 1, 38, 138, 47, 59, 25, 130, 154, 40, 103, 151, 50, 119, 120, 15, 11, 242, 117, 232, 216, 173, 222, 214, 6, 84, 126, 28, 115, 200, 237, 122, 97, 188, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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