Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1457504cbe8e93f2af9994d8dd5ce7922f21c3360868e0ecc808249610558a03

Tx prefix hash: 4d9310984cfffef1293c5792f52feb935500f2a0f9d49a6b298b076deca9a3ff
Tx public key: 4f7d7b5718b090b3ad17346fb6ac846d014d2592a6eeb7f0afc747582ef05a4f
Timestamp: 1704926203 Timestamp [UCT]: 2024-01-10 22:36:43 Age [y:d:h:m:s]: 01:304:08:55:14
Block: 932571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476366 RingCT/type: yes/0
Extra: 014f7d7b5718b090b3ad17346fb6ac846d014d2592a6eeb7f0afc747582ef05a4f0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b82835185481018b73009211a9e7b3bdf3ef505e082309ef0ffd4ff2bd99ed1 0.600000000000 1390507 of 15

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": 932581, "vin": [ { "gen": { "height": 932571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b82835185481018b73009211a9e7b3bdf3ef505e082309ef0ffd4ff2bd99ed1" } } ], "extra": [ 1, 79, 125, 123, 87, 24, 176, 144, 179, 173, 23, 52, 111, 182, 172, 132, 109, 1, 77, 37, 146, 166, 238, 183, 240, 175, 199, 71, 88, 46, 240, 90, 79, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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