Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df35b755ce5bf3a45661a820ce006305f97d8dfc6a21e25e417b978f23ca0bc

Tx prefix hash: 7ad6b824cf21158659eab6fb931b13d5f0cc3a416978754508f4210821bf5f4f
Tx public key: a809d69c1c60f237ef71d1a4170b537dae3eece2ed8dbe3b7af290550afd6a97
Timestamp: 1724345877 Timestamp [UCT]: 2024-08-22 16:57:57 Age [y:d:h:m:s]: 00:217:16:47:08
Block: 1093594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155440 RingCT/type: yes/0
Extra: 01a809d69c1c60f237ef71d1a4170b537dae3eece2ed8dbe3b7af290550afd6a97021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9f3c1dbacc1f448f924aabe2431d446c181d729cf51f468bb55ecc51c6e8a48 0.600000000000 1568569 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": 1093604, "vin": [ { "gen": { "height": 1093594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9f3c1dbacc1f448f924aabe2431d446c181d729cf51f468bb55ecc51c6e8a48" } } ], "extra": [ 1, 168, 9, 214, 156, 28, 96, 242, 55, 239, 113, 209, 164, 23, 11, 83, 125, 174, 62, 236, 226, 237, 141, 190, 59, 122, 242, 144, 85, 10, 253, 106, 151, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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