Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3891b7e98da4d4cd255fbf69c1c021b8b3040cf48e4688c4a37617f00d50a12

Tx prefix hash: 4f25676c3bea92d22f432433643e9f013d7520ef19573de0e735c2ab813faa33
Tx public key: d7e84544c6aae9ab23137ab82be55e52be1c11a35bb515148095b3d1b4477f0c
Timestamp: 1684080075 Timestamp [UCT]: 2023-05-14 16:01:15 Age [y:d:h:m:s]: 01:248:13:58:18
Block: 760014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439100 RingCT/type: yes/0
Extra: 01d7e84544c6aae9ab23137ab82be55e52be1c11a35bb515148095b3d1b4477f0c021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.861051150000 dcy

stealth address amount amount idx
00: 01bfa09d4a63b17dab7777ebf07ffd345face19359a415e2349dc4d75560876f 1.861051150000 1208605 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": 760024, "vin": [ { "gen": { "height": 760014 } } ], "vout": [ { "amount": 1861051150, "target": { "key": "01bfa09d4a63b17dab7777ebf07ffd345face19359a415e2349dc4d75560876f" } } ], "extra": [ 1, 215, 232, 69, 68, 198, 170, 233, 171, 35, 19, 122, 184, 43, 229, 94, 82, 190, 28, 17, 163, 91, 181, 21, 20, 128, 149, 179, 209, 180, 71, 127, 12, 2, 17, 0, 0, 0, 2, 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