Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b4ff9e19df13465ed4bf05b5717984a394d50b149a312ccb4e684e762b3b50

Tx prefix hash: 262e185fd3ac94e6c7f2aab1e950ba8fa9f8a9b04cbe6f79e47df6e4def12422
Tx public key: e9ca989dbef8639ea59d8c77819fe2449f7718c83deea91434e00c028480cc03
Timestamp: 1649568840 Timestamp [UCT]: 2022-04-10 05:34:00 Age [y:d:h:m:s]: 02:309:14:36:44
Block: 477060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740827 RingCT/type: yes/0
Extra: 01e9ca989dbef8639ea59d8c77819fe2449f7718c83deea91434e00c028480cc03021100000002d3fcec30000000000000000000

1 output(s) for total of 16.117676031000 dcy

stealth address amount amount idx
00: 309f83a2b7424f4d658f9b26cfda0867aa2e8c23fe083f30d6aa2ac294324f21 16.117676031000 897675 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": 477070, "vin": [ { "gen": { "height": 477060 } } ], "vout": [ { "amount": 16117676031, "target": { "key": "309f83a2b7424f4d658f9b26cfda0867aa2e8c23fe083f30d6aa2ac294324f21" } } ], "extra": [ 1, 233, 202, 152, 157, 190, 248, 99, 158, 165, 157, 140, 119, 129, 159, 226, 68, 159, 119, 24, 200, 61, 238, 169, 20, 52, 224, 12, 2, 132, 128, 204, 3, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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