Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cd765463e1b45e2dd369a0f1a608ef4150647e288a383039f5814a1b776907d

Tx prefix hash: c89ec08e4e112b3ee414f7c0fd4b9af3ffc2369827a63819d3a9d552174c0fc0
Tx public key: 46230311f5b81c4b37dbc8f17dad505c0bee4837c5a55bed5d69670c1c619f93
Timestamp: 1577942850 Timestamp [UCT]: 2020-01-02 05:27:30 Age [y:d:h:m:s]: 05:032:04:25:45
Block: 36948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172756 RingCT/type: yes/0
Extra: 0146230311f5b81c4b37dbc8f17dad505c0bee4837c5a55bed5d69670c1c619f930211000000034943cd9f000000000000000000

1 output(s) for total of 462.995521607000 dcy

stealth address amount amount idx
00: f0ad53aff08794a5f70f013b701e7f7379ec6f821189f05360e3764098754cf8 462.995521607000 62644 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": 36958, "vin": [ { "gen": { "height": 36948 } } ], "vout": [ { "amount": 462995521607, "target": { "key": "f0ad53aff08794a5f70f013b701e7f7379ec6f821189f05360e3764098754cf8" } } ], "extra": [ 1, 70, 35, 3, 17, 245, 184, 28, 75, 55, 219, 200, 241, 125, 173, 80, 92, 11, 238, 72, 55, 197, 165, 91, 237, 93, 105, 103, 12, 28, 97, 159, 147, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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