Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b150735502366a105b92daa0c0292461be0104d02a5c4e269d9966b6a09bef

Tx prefix hash: b44aa8edb246401bf96db222d6e0ebed26c3f1d602991184668c7094bbf6f036
Tx public key: 8cc8e5aa44cc9ddd11a9f658cc9a1a3ad6168895097d8fa2b2e041eb586a0f64
Timestamp: 1688254138 Timestamp [UCT]: 2023-07-01 23:28:58 Age [y:d:h:m:s]: 01:349:07:24:40
Block: 794626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510739 RingCT/type: yes/0
Extra: 018cc8e5aa44cc9ddd11a9f658cc9a1a3ad6168895097d8fa2b2e041eb586a0f64021100000001faf35c9c000000000000000000

1 output(s) for total of 1.429138552000 dcy

stealth address amount amount idx
00: ffe73f1e8ae8290fd981361d44cf19edcd1f36972394897682caeba871caf592 1.429138552000 1245389 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": 794636, "vin": [ { "gen": { "height": 794626 } } ], "vout": [ { "amount": 1429138552, "target": { "key": "ffe73f1e8ae8290fd981361d44cf19edcd1f36972394897682caeba871caf592" } } ], "extra": [ 1, 140, 200, 229, 170, 68, 204, 157, 221, 17, 169, 246, 88, 204, 154, 26, 58, 214, 22, 136, 149, 9, 125, 143, 162, 178, 224, 65, 235, 88, 106, 15, 100, 2, 17, 0, 0, 0, 1, 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