Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b0ab1cd05ecdad60dfa018d60c27d624cb3a3656072ccddb59177b9f67b0cf

Tx prefix hash: fa6fc97fb3b14ca124c601119aa69cf49bdef6f67ff7009603e6ca7e3d8a036a
Tx public key: 8b5e128337ea9552ef1e96a8ff1c92a3d2df630959e8834f5730a0e7693f3d66
Timestamp: 1714381395 Timestamp [UCT]: 2024-04-29 09:03:15 Age [y:d:h:m:s]: 00:344:07:43:37
Block: 1010973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246138 RingCT/type: yes/0
Extra: 018b5e128337ea9552ef1e96a8ff1c92a3d2df630959e8834f5730a0e7693f3d660211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99bf154199cf5cdcf8132641080923ab4339e4b44446cd4cf5d0d963a107a54f 0.600000000000 1473071 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": 1010983, "vin": [ { "gen": { "height": 1010973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99bf154199cf5cdcf8132641080923ab4339e4b44446cd4cf5d0d963a107a54f" } } ], "extra": [ 1, 139, 94, 18, 131, 55, 234, 149, 82, 239, 30, 150, 168, 255, 28, 146, 163, 210, 223, 99, 9, 89, 232, 131, 79, 87, 48, 160, 231, 105, 63, 61, 102, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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