Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2435a05e6a35f8954cec2fb717e7efc5433b7e55915dba1f21beee1f64964c

Tx prefix hash: cf536460f1dd2a398a1e9e702a222dbbca275e5bc912c83a4719e4f8465c0f3a
Tx public key: f8cd0612d0778c1fe27c2a097da8b255c751d2a469a7f11319a24c14b43f6ef3
Timestamp: 1724048676 Timestamp [UCT]: 2024-08-19 06:24:36 Age [y:d:h:m:s]: 00:245:20:44:29
Block: 1091127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175586 RingCT/type: yes/0
Extra: 01f8cd0612d0778c1fe27c2a097da8b255c751d2a469a7f11319a24c14b43f6ef3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d66a2a86c7547c1d333d9239e0f3d72dfe7102973c883de619e5a7826af8e50 0.600000000000 1565756 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": 1091137, "vin": [ { "gen": { "height": 1091127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d66a2a86c7547c1d333d9239e0f3d72dfe7102973c883de619e5a7826af8e50" } } ], "extra": [ 1, 248, 205, 6, 18, 208, 119, 140, 31, 226, 124, 42, 9, 125, 168, 178, 85, 199, 81, 210, 164, 105, 167, 241, 19, 25, 162, 76, 20, 180, 63, 110, 243, 2, 17, 0, 0, 0, 4, 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