Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2499da1049fd7997f7da103d0350c6a0fd35e77c6c65de1840d78a0f918228

Tx prefix hash: a60ca8e90c82aa5db0493815b229f4e05760b88c13ea2f209094862ded13c5a4
Tx public key: 5992e3690203eea7332fd72a3dd78c3002375c8ae6ea7a93b2452719bffb8fe6
Timestamp: 1684652960 Timestamp [UCT]: 2023-05-21 07:09:20 Age [y:d:h:m:s]: 02:011:12:36:13
Block: 764765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530356 RingCT/type: yes/0
Extra: 015992e3690203eea7332fd72a3dd78c3002375c8ae6ea7a93b2452719bffb8fe602110000000a75e3f0e9000000000000000000

1 output(s) for total of 1.794800854000 dcy

stealth address amount amount idx
00: 4d3a6b9d980cb34d49ca411f17c0cfcfd3c18118bb133fb34b7d4be3d57e1a41 1.794800854000 1213718 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": 764775, "vin": [ { "gen": { "height": 764765 } } ], "vout": [ { "amount": 1794800854, "target": { "key": "4d3a6b9d980cb34d49ca411f17c0cfcfd3c18118bb133fb34b7d4be3d57e1a41" } } ], "extra": [ 1, 89, 146, 227, 105, 2, 3, 238, 167, 51, 47, 215, 42, 61, 215, 140, 48, 2, 55, 92, 138, 230, 234, 122, 147, 178, 69, 39, 25, 191, 251, 143, 230, 2, 17, 0, 0, 0, 10, 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