Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3454b59e0b4b88930b807a559926d0962531ba85c19aa5e859f856e311d60874

Tx prefix hash: 84935c7047cb7b5a67187fa2648a6180a5f2d8d9cab2edff37d32fc212ae3c77
Tx public key: a797ac993a7ac82938927192e640b53de5cd715192f1efa1f22a3d87891fb73e
Timestamp: 1761197281 Timestamp [UTC]: 2025-10-23 05:28:01 Age [y:d:h:m:s]: 01:025:22:00:54
Block: 1395994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284857 RingCT/type: yes/0
Extra: 01a797ac993a7ac82938927192e640b53de5cd715192f1efa1f22a3d87891fb73e021100000005df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d11deaefa6e72d2d02e9fd90f88df36857cb466ad4dab3301334a542a8ce1c3 0.000600000000 1884277 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": 1396004, "vin": [ { "gen": { "height": 1395994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d11deaefa6e72d2d02e9fd90f88df36857cb466ad4dab3301334a542a8ce1c3" } } ], "extra": [ 1, 167, 151, 172, 153, 58, 122, 200, 41, 56, 146, 113, 146, 230, 64, 181, 61, 229, 205, 113, 81, 146, 241, 239, 161, 242, 42, 61, 135, 137, 31, 183, 62, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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: