Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d999e43d2438cebb30361345fcb727c5f4f212b86bb81d13030fcc4f7da9cba1

Tx prefix hash: c09212d7b3be6e15aa1a9623c835227fa63cc3eda94708745c0a9ac8f314bdaa
Tx public key: 448fe502c3e86c370d017052b6daf6eb00c6f22e945cc7643c48f838114b5622
Timestamp: 1737176382 Timestamp [UCT]: 2025-01-18 04:59:42 Age [y:d:h:m:s]: 00:151:02:08:42
Block: 1199806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107689 RingCT/type: yes/0
Extra: 01448fe502c3e86c370d017052b6daf6eb00c6f22e945cc7643c48f838114b56220211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ecf8d2f60f74235777e9b8ce962df8e550dccd3cb20ffc4505cd3fad89ce98b 0.600000000000 1686439 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": 1199816, "vin": [ { "gen": { "height": 1199806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ecf8d2f60f74235777e9b8ce962df8e550dccd3cb20ffc4505cd3fad89ce98b" } } ], "extra": [ 1, 68, 143, 229, 2, 195, 232, 108, 55, 13, 1, 112, 82, 182, 218, 246, 235, 0, 198, 242, 46, 148, 92, 199, 100, 60, 72, 248, 56, 17, 75, 86, 34, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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