Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be52b0a781b49911845f831a02293bb0aa6180863d1f80794a552e6d7f12a459

Tx prefix hash: caff910cd6d41c3bcdcc89f11aa7d2762b21be5b38bb69ba6d676575ee1a91b8
Tx public key: 790392a7512c8f691b7483f986bc8debfe8f67dbef6c610ccf0e4a72b26625b9
Timestamp: 1697913009 Timestamp [UCT]: 2023-10-21 18:30:09 Age [y:d:h:m:s]: 01:092:12:59:11
Block: 874644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327342 RingCT/type: yes/0
Extra: 01790392a7512c8f691b7483f986bc8debfe8f67dbef6c610ccf0e4a72b26625b902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.776142324000 dcy

stealth address amount amount idx
00: ca22c22e9612070233a1e3b059c7232707179262b5703821941a556e58688743 0.776142324000 1329866 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": 874654, "vin": [ { "gen": { "height": 874644 } } ], "vout": [ { "amount": 776142324, "target": { "key": "ca22c22e9612070233a1e3b059c7232707179262b5703821941a556e58688743" } } ], "extra": [ 1, 121, 3, 146, 167, 81, 44, 143, 105, 27, 116, 131, 249, 134, 188, 141, 235, 254, 143, 103, 219, 239, 108, 97, 12, 207, 14, 74, 114, 178, 102, 37, 185, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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