Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ff9befee8ec3c5b2a50c265d3aa93ad86ab2fb2edff7048c3e2d6521a39b9f

Tx prefix hash: b094c4ea5805880eb0f3482b8ebba0b514fad797a8231f2ed810a994cdeaf3fa
Tx public key: 649a0eebd463786e59f9fcc543b09ad60e0efc24731b0d2f5ae1fc6fd72834f7
Timestamp: 1771062081 Timestamp [UTC]: 2026-02-14 09:41:21 Age [y:d:h:m:s]: 00:275:02:30:49
Block: 1477531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202110 RingCT/type: yes/0
Extra: 01649a0eebd463786e59f9fcc543b09ad60e0efc24731b0d2f5ae1fc6fd72834f7021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9c82a0a08baff6693d5c57338eaf93364670e1b1af1f6692fbbec64e0a5884e5 0.000600000000 1966849 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": 1477541, "vin": [ { "gen": { "height": 1477531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c82a0a08baff6693d5c57338eaf93364670e1b1af1f6692fbbec64e0a5884e5" } } ], "extra": [ 1, 100, 154, 14, 235, 212, 99, 120, 110, 89, 249, 252, 197, 67, 176, 154, 214, 14, 14, 252, 36, 115, 27, 13, 47, 90, 225, 252, 111, 215, 40, 52, 247, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: