Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c5a998719d7d5913e74b76e788ef73ee4f9a9eefe2f5d03d32aae5fff921a28

Tx prefix hash: f65ade15496bfd0d5b1feb470afb9001499c77820eb9f41c47605b4b0270d499
Tx public key: 9bf7bec5a5d31026bde4da6e5dea147a2e5ae93d2e83e612d9c7d7daef15078f
Timestamp: 1758944523 Timestamp [UTC]: 2025-09-27 03:42:03 Age [y:d:h:m:s]: 00:330:20:36:24
Block: 1377310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242261 RingCT/type: yes/0
Extra: 019bf7bec5a5d31026bde4da6e5dea147a2e5ae93d2e83e612d9c7d7daef15078f021100000006a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 56f2b59156b9d3d0b01b65112cd2ecd129e098602cc656dfec2942495318020e 0.000600000000 1865401 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": 1377320, "vin": [ { "gen": { "height": 1377310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56f2b59156b9d3d0b01b65112cd2ecd129e098602cc656dfec2942495318020e" } } ], "extra": [ 1, 155, 247, 190, 197, 165, 211, 16, 38, 189, 228, 218, 110, 93, 234, 20, 122, 46, 90, 233, 61, 46, 131, 230, 18, 217, 199, 215, 218, 239, 21, 7, 143, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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: