Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08cd1eb7935474669261524a8cad3b9f24dbee596e3e8066f3dedfadfd0eff00

Tx prefix hash: 717f9600a2d21d1ed9663f4f4715ef530a484c64ce060d5e42fb5b8618591612
Tx public key: 5fb9eb6f3b7a5fd318005f0f436ef27d914d5f13f47cf73ce957aa952be8f641
Timestamp: 1675465284 Timestamp [UCT]: 2023-02-03 23:01:24 Age [y:d:h:m:s]: 02:064:04:25:29
Block: 689222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567478 RingCT/type: yes/0
Extra: 015fb9eb6f3b7a5fd318005f0f436ef27d914d5f13f47cf73ce957aa952be8f641021100000003e6d27f9c000000000000000000

1 output(s) for total of 3.193900140000 dcy

stealth address amount amount idx
00: e418e9c76a40db8c156fede44c29ae35499348c2f19249ca99df70a0e90ca3b8 3.193900140000 1131886 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": 689232, "vin": [ { "gen": { "height": 689222 } } ], "vout": [ { "amount": 3193900140, "target": { "key": "e418e9c76a40db8c156fede44c29ae35499348c2f19249ca99df70a0e90ca3b8" } } ], "extra": [ 1, 95, 185, 235, 111, 59, 122, 95, 211, 24, 0, 95, 15, 67, 110, 242, 125, 145, 77, 95, 19, 244, 124, 247, 60, 233, 87, 170, 149, 43, 232, 246, 65, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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