Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa0c667aa87355aa177eb06022ee0f13a925a9cd463fc5bfb48b3c49bb3a25e

Tx prefix hash: a075e2dfc4c93f4a1ee4eff59da543d4da5a8635ba88a88ede29b310f4951086
Tx public key: 95db3ac6a2a4f29bb71cd961dc3e65bd517c959b9b320a1b362c02a44fb35e3b
Timestamp: 1755824022 Timestamp [UTC]: 2025-08-22 00:53:42 Age [y:d:h:m:s]: 01:089:13:52:25
Block: 1351636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330317 RingCT/type: yes/0
Extra: 0195db3ac6a2a4f29bb71cd961dc3e65bd517c959b9b320a1b362c02a44fb35e3b021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf33445d782d4510434118c272c87305b08d9a5ee2e258d2e870a29fa7af7870 0.000600000000 1839593 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": 1351646, "vin": [ { "gen": { "height": 1351636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf33445d782d4510434118c272c87305b08d9a5ee2e258d2e870a29fa7af7870" } } ], "extra": [ 1, 149, 219, 58, 198, 162, 164, 242, 155, 183, 28, 217, 97, 220, 62, 101, 189, 81, 124, 149, 155, 155, 50, 10, 27, 54, 44, 2, 164, 79, 179, 94, 59, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: