Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1745d41d785df80bf4554cb91e8eaeba5a30c6b596ca00f18dffb60d2794a60d

Tx prefix hash: 432b20ed215a39070c42b807040005379844ccd795d3d20f5e9b91e5c0574e93
Tx public key: 099d269433acf8b0a2484750f020f4fd96e6858e011b1ff9540fef454c72611f
Timestamp: 1773799467 Timestamp [UTC]: 2026-03-18 02:04:27 Age [y:d:h:m:s]: 00:241:11:48:21
Block: 1500173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178006 RingCT/type: yes/0
Extra: 01099d269433acf8b0a2484750f020f4fd96e6858e011b1ff9540fef454c72611f021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4dd1c14dc97d1e50203d54a5b505ebcbe67893aec596e6863459fa92a1ae737f 0.000600000000 1989843 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": 1500183, "vin": [ { "gen": { "height": 1500173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dd1c14dc97d1e50203d54a5b505ebcbe67893aec596e6863459fa92a1ae737f" } } ], "extra": [ 1, 9, 157, 38, 148, 51, 172, 248, 176, 162, 72, 71, 80, 240, 32, 244, 253, 150, 230, 133, 142, 1, 27, 31, 249, 84, 15, 239, 69, 76, 114, 97, 31, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: