Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c4ebd3b6e918dcb5a59f0a640bc1c046103d7feba0871bc9fa55cf9ee4ed63

Tx prefix hash: 81e795cb3792a3fd95c3aae443457b6a4300ac0229fa1a786342697e39e4687b
Tx public key: d2b4540b7269bfd8135886d579970f153ae382e12c3f7fc21f52e7a58d399e09
Timestamp: 1726360741 Timestamp [UCT]: 2024-09-15 00:39:01 Age [y:d:h:m:s]: 00:077:05:26:15
Block: 1110282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55231 RingCT/type: yes/0
Extra: 01d2b4540b7269bfd8135886d579970f153ae382e12c3f7fc21f52e7a58d399e09021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a00818dced77bfc89c7366bbc35b34bb31a70bae0b9aac8de74db0077e9371e 0.600000000000 1588831 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": 1110292, "vin": [ { "gen": { "height": 1110282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a00818dced77bfc89c7366bbc35b34bb31a70bae0b9aac8de74db0077e9371e" } } ], "extra": [ 1, 210, 180, 84, 11, 114, 105, 191, 216, 19, 88, 134, 213, 121, 151, 15, 21, 58, 227, 130, 225, 44, 63, 127, 194, 31, 82, 231, 165, 141, 57, 158, 9, 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