Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e798004bf86a0548b17686602d026f997a40ec6f5fab0339fbd9cfa7c6b2cbec

Tx prefix hash: 25ce38b081370a12f7fe7d0271380772b5392aa4e9d31e715aeae39c5b5f447c
Tx public key: f922f8dd2695aa7a391a8239b83abfbdc4a19544c1dc0da46c9a2e4e50f274e9
Timestamp: 1699830006 Timestamp [UCT]: 2023-11-12 23:00:06 Age [y:d:h:m:s]: 01:079:23:45:00
Block: 890347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318306 RingCT/type: yes/0
Extra: 01f922f8dd2695aa7a391a8239b83abfbdc4a19544c1dc0da46c9a2e4e50f274e9021100000007faf35c9c000000000000000000

1 output(s) for total of 0.688510846000 dcy

stealth address amount amount idx
00: 1ccbc761f2304e011bc700e39dd2903cff4a34797f262cc745effce3731e70b9 0.688510846000 1346370 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": 890357, "vin": [ { "gen": { "height": 890347 } } ], "vout": [ { "amount": 688510846, "target": { "key": "1ccbc761f2304e011bc700e39dd2903cff4a34797f262cc745effce3731e70b9" } } ], "extra": [ 1, 249, 34, 248, 221, 38, 149, 170, 122, 57, 26, 130, 57, 184, 58, 191, 189, 196, 161, 149, 68, 193, 220, 13, 164, 108, 154, 46, 78, 80, 242, 116, 233, 2, 17, 0, 0, 0, 7, 250, 243, 92, 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