Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b3fc17e0ca08a47357b75e007fa2f6b3d4935acf1bf1805695e23bb11c926f

Tx prefix hash: 33d02d21c46eccca97aeb93be20e7a516cf7a140baaee9490aa017b4f829abc5
Tx public key: 1b6450cee77460f95bbadf172c79370b71ff3ce8dad64ed0c8a5607597782636
Timestamp: 1696254445 Timestamp [UCT]: 2023-10-02 13:47:25 Age [y:d:h:m:s]: 01:149:01:05:21
Block: 860896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367538 RingCT/type: yes/0
Extra: 011b6450cee77460f95bbadf172c79370b71ff3ce8dad64ed0c8a5607597782636021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.861974102000 dcy

stealth address amount amount idx
00: e971ac63af9952fb6f9602c1e0d566913b7aa4ae75644b18b88d0d7f7ff8de57 0.861974102000 1315206 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": 860906, "vin": [ { "gen": { "height": 860896 } } ], "vout": [ { "amount": 861974102, "target": { "key": "e971ac63af9952fb6f9602c1e0d566913b7aa4ae75644b18b88d0d7f7ff8de57" } } ], "extra": [ 1, 27, 100, 80, 206, 231, 116, 96, 249, 91, 186, 223, 23, 44, 121, 55, 11, 113, 255, 60, 232, 218, 214, 78, 208, 200, 165, 96, 117, 151, 120, 38, 54, 2, 17, 0, 0, 0, 1, 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