Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06c0e97beaac8d716207579dd6fafc10c9a1046c3327af687e9d555a1f924249

Tx prefix hash: 2ce9ef723174cf3c00294af099b958f722b5f83b76d11222c65c0847abf1b2a9
Tx public key: ae102eebe1b74cb17b24e7cd52d217d4f441e69449390428d2a7fae671ac47e5
Timestamp: 1708600707 Timestamp [UCT]: 2024-02-22 11:18:27 Age [y:d:h:m:s]: 01:033:00:00:04
Block: 963050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284583 RingCT/type: yes/0
Extra: 01ae102eebe1b74cb17b24e7cd52d217d4f441e69449390428d2a7fae671ac47e502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38e31a6c6bf1b03088a40215c37c282c1f47847a767cc154e05cf1ca2c2157ce 0.600000000000 1422747 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": 963060, "vin": [ { "gen": { "height": 963050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38e31a6c6bf1b03088a40215c37c282c1f47847a767cc154e05cf1ca2c2157ce" } } ], "extra": [ 1, 174, 16, 46, 235, 225, 183, 76, 177, 123, 36, 231, 205, 82, 210, 23, 212, 244, 65, 230, 148, 73, 57, 4, 40, 210, 167, 250, 230, 113, 172, 71, 229, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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