Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 064ce827f8d073c6821fe4fb5c0dbf41b53bd42a643657ee0acedcd7d02afbec

Tx prefix hash: cad251b2f5475b7d35927a55e685f00e114a3d5accec57a4707ba5e83290788f
Tx public key: b1f41f6b6d681c759e5b898dad0ee3809a84e026e59197edbbc4e60724af8558
Timestamp: 1685869606 Timestamp [UCT]: 2023-06-04 09:06:46 Age [y:d:h:m:s]: 01:164:16:40:12
Block: 774844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379074 RingCT/type: yes/0
Extra: 01b1f41f6b6d681c759e5b898dad0ee3809a84e026e59197edbbc4e60724af8558021100000002faf35c9c000000000000000000

1 output(s) for total of 1.661959138000 dcy

stealth address amount amount idx
00: 7ed0e15c04db0014d141aa7c64bc739738215e1bca3074226b3267174a4d61cf 1.661959138000 1224331 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": 774854, "vin": [ { "gen": { "height": 774844 } } ], "vout": [ { "amount": 1661959138, "target": { "key": "7ed0e15c04db0014d141aa7c64bc739738215e1bca3074226b3267174a4d61cf" } } ], "extra": [ 1, 177, 244, 31, 107, 109, 104, 28, 117, 158, 91, 137, 141, 173, 14, 227, 128, 154, 132, 224, 38, 229, 145, 151, 237, 187, 196, 230, 7, 36, 175, 133, 88, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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