Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260432076fde1c1db0ce33cd6610cbd8ecf6154b17109f651ab057bab2cfef51

Tx prefix hash: 05e3ae5cc46fc021cf3588779141ab545c90b72b0cc2f737c3f11848a836ff89
Tx public key: b731262e9d8634175f1f2a879aa3b234500ed0d2e2abeeffe191ab5081f9e262
Timestamp: 1581948890 Timestamp [UCT]: 2020-02-17 14:14:50 Age [y:d:h:m:s]: 04:317:01:40:28
Block: 66818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118999 RingCT/type: yes/0
Extra: 01b731262e9d8634175f1f2a879aa3b234500ed0d2e2abeeffe191ab5081f9e26202110000000156c366d3000000000000000000

1 output(s) for total of 368.642189519000 dcy

stealth address amount amount idx
00: 4455e5f3c47aa76c06c9dcea51a540a31f13df54462f5619dd7376cc476f6a94 368.642189519000 123028 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": 66828, "vin": [ { "gen": { "height": 66818 } } ], "vout": [ { "amount": 368642189519, "target": { "key": "4455e5f3c47aa76c06c9dcea51a540a31f13df54462f5619dd7376cc476f6a94" } } ], "extra": [ 1, 183, 49, 38, 46, 157, 134, 52, 23, 95, 31, 42, 135, 154, 163, 178, 52, 80, 14, 208, 210, 226, 171, 238, 255, 225, 145, 171, 80, 129, 249, 226, 98, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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