Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536d942e44d6e448d5a3aa7e6d8615495d97ca9ba97be0ec7c440509ec9b719f

Tx prefix hash: c698fee5a7750a67dcc174e977e19379443e58526fb60e68ffdd5212bd2fba6b
Tx public key: 3cb53eec361a22c034bd226760dcc1dd10d2e7b12ee856ae657c888b24039b62
Timestamp: 1757238856 Timestamp [UTC]: 2025-09-07 09:54:16 Age [y:d:h:m:s]: 01:073:20:59:57
Block: 1363275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319211 RingCT/type: yes/0
Extra: 013cb53eec361a22c034bd226760dcc1dd10d2e7b12ee856ae657c888b24039b62021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 98987b9bcaaea10e8fddb53955e74548e2d0a6221530c660d6dc4d7c8d683a7f 0.000600000000 1851314 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": 1363285, "vin": [ { "gen": { "height": 1363275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98987b9bcaaea10e8fddb53955e74548e2d0a6221530c660d6dc4d7c8d683a7f" } } ], "extra": [ 1, 60, 181, 62, 236, 54, 26, 34, 192, 52, 189, 34, 103, 96, 220, 193, 221, 16, 210, 231, 177, 46, 232, 86, 174, 101, 124, 136, 139, 36, 3, 155, 98, 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: