Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53705353ed1e8af8fd1a2aa39780bb623127b619e7f487e4414f7d09eebc043f

Tx prefix hash: f5a57fe80fb4686b00c3db2c47ac518d60d6e7ccf6a7deae5257f36a454a68da
Tx public key: 44876721b491e3578dfd14ee8d1e56e49a96d04b35a9176e7f42cf5c3a1a5721
Timestamp: 1752858963 Timestamp [UTC]: 2025-07-18 17:16:03 Age [y:d:h:m:s]: 01:119:15:14:29
Block: 1328254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350519 RingCT/type: yes/0
Extra: 0144876721b491e3578dfd14ee8d1e56e49a96d04b35a9176e7f42cf5c3a1a57210211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 03b9484c7e3d182b3eaa53ad54ccaddc931a4b34ba264543d4f4d84675ad9e6c 0.000600000000 1816015 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 dinastycoin-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": 1328264, "vin": [ { "gen": { "height": 1328254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b9484c7e3d182b3eaa53ad54ccaddc931a4b34ba264543d4f4d84675ad9e6c" } } ], "extra": [ 1, 68, 135, 103, 33, 180, 145, 227, 87, 141, 253, 20, 238, 141, 30, 86, 228, 154, 150, 208, 75, 53, 169, 23, 110, 127, 66, 207, 92, 58, 26, 87, 33, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: