Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c5924ff5a3c98655b7d0e490e326a920ed25ded915d76fbc8ed9678924937b

Tx prefix hash: 59c4cbe9a40c48a841997a2abbb83b7d98a98c403223b9bd3018eccaea2b89f2
Tx public key: 33e9a2101b649fce65c486f385d3708cda24283f624c121c7c020d30cfb12e0a
Timestamp: 1736185477 Timestamp [UCT]: 2025-01-06 17:44:37 Age [y:d:h:m:s]: 00:163:06:46:30
Block: 1191613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116395 RingCT/type: yes/0
Extra: 0133e9a2101b649fce65c486f385d3708cda24283f624c121c7c020d30cfb12e0a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ce56f6cffad6448d5d3b3648f97ce025d90823a821052f1d41130972870592 0.600000000000 1678154 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": 1191623, "vin": [ { "gen": { "height": 1191613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ce56f6cffad6448d5d3b3648f97ce025d90823a821052f1d41130972870592" } } ], "extra": [ 1, 51, 233, 162, 16, 27, 100, 159, 206, 101, 196, 134, 243, 133, 211, 112, 140, 218, 36, 40, 63, 98, 76, 18, 28, 124, 2, 13, 48, 207, 177, 46, 10, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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