Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7d0605762b8624c91d7b17e79115e90b48fa9346dfdffe2eeee1bd055b9f67

Tx prefix hash: f0fe68862a3c2cf976f2c298ab9ec9f63b5278e73a02003e068ad722c946c6d3
Tx public key: 7c689f65f023e625e64342e9e62fb9d3d443d47126bfbaf4f9bbb277cc193d46
Timestamp: 1709870965 Timestamp [UCT]: 2024-03-08 04:09:25 Age [y:d:h:m:s]: 01:249:07:01:21
Block: 973591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436882 RingCT/type: yes/0
Extra: 017c689f65f023e625e64342e9e62fb9d3d443d47126bfbaf4f9bbb277cc193d460211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b62300b80eb7e5dd1b95c27a5f612088accb5383e5de7987b4dab6a353fc768d 0.600000000000 1433526 of 15

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": 973601, "vin": [ { "gen": { "height": 973591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b62300b80eb7e5dd1b95c27a5f612088accb5383e5de7987b4dab6a353fc768d" } } ], "extra": [ 1, 124, 104, 159, 101, 240, 35, 230, 37, 230, 67, 66, 233, 230, 47, 185, 211, 212, 67, 212, 113, 38, 191, 186, 244, 249, 187, 178, 119, 204, 25, 61, 70, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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