Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc611690ab2b95e8699d6e68aaf8fa065c5c255fe357e442490fd00737dd700d

Tx prefix hash: bfd8eec58aea2502d269fd26d33084e22ed0ac6e7ec2be5279ca92915860a146
Tx public key: 9f1fcdd199f4c7f2fdb36bb8eca93e0fbd8267dab19da41b3f37efd63d5cf89f
Timestamp: 1765538104 Timestamp [UTC]: 2025-12-12 11:15:04 Age [y:d:h:m:s]: 00:148:21:20:02
Block: 1431954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99015 RingCT/type: yes/0
Extra: 019f1fcdd199f4c7f2fdb36bb8eca93e0fbd8267dab19da41b3f37efd63d5cf89f021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed1f72d28548945dbe51f3d283d3543826a9b43c929e934295011ff04e9f6682 0.000600000000 1920731 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": 1431964, "vin": [ { "gen": { "height": 1431954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed1f72d28548945dbe51f3d283d3543826a9b43c929e934295011ff04e9f6682" } } ], "extra": [ 1, 159, 31, 205, 209, 153, 244, 199, 242, 253, 179, 107, 184, 236, 169, 62, 15, 189, 130, 103, 218, 177, 157, 164, 27, 63, 55, 239, 214, 61, 92, 248, 159, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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: