Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 802b94fbe44eec60a409d6fd7ba4348be81726e7e85ef8af152f8df392ed8d05

Tx prefix hash: b2805b698b182e2efb4dad339259f7747081ac0e69b3967608653abbdd2d2dd9
Tx public key: e2ab648e8ae926630c603b68d186c3f3d66cdd1df226dcde81e659291e6977dc
Timestamp: 1725032740 Timestamp [UCT]: 2024-08-30 15:45:40 Age [y:d:h:m:s]: 00:241:03:48:59
Block: 1099274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172235 RingCT/type: yes/0
Extra: 01e2ab648e8ae926630c603b68d186c3f3d66cdd1df226dcde81e659291e6977dc021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3804bcdb0c4828d5efa92a5b75d42d51b463ae0e3ae1e14b1f8a67418b7eaf13 0.600000000000 1575231 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": 1099284, "vin": [ { "gen": { "height": 1099274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3804bcdb0c4828d5efa92a5b75d42d51b463ae0e3ae1e14b1f8a67418b7eaf13" } } ], "extra": [ 1, 226, 171, 100, 142, 138, 233, 38, 99, 12, 96, 59, 104, 209, 134, 195, 243, 214, 108, 221, 29, 242, 38, 220, 222, 129, 230, 89, 41, 30, 105, 119, 220, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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