Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6268917ea605426270e2f3f68464a12e262ec235c7af1f3f43ffa655d7f182f

Tx prefix hash: 7f0f9afd442da53362a9a6bde901630b18e7f716deec96c23cee9bcfdba74a64
Tx public key: 032c08c28271cbb7fc6d68d9d744d8863bd54dcac49e0b56a3977aabcfe5cb60
Timestamp: 1761145800 Timestamp [UTC]: 2025-10-22 15:10:00 Age [y:d:h:m:s]: 01:030:04:24:13
Block: 1395568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287926 RingCT/type: yes/0
Extra: 01032c08c28271cbb7fc6d68d9d744d8863bd54dcac49e0b56a3977aabcfe5cb60021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0f6e1d89d28c679b337cee90cc0921d8adb3cc2505518bc47c6645a838b207b6 0.000600000000 1883849 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": 1395578, "vin": [ { "gen": { "height": 1395568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f6e1d89d28c679b337cee90cc0921d8adb3cc2505518bc47c6645a838b207b6" } } ], "extra": [ 1, 3, 44, 8, 194, 130, 113, 203, 183, 252, 109, 104, 217, 215, 68, 216, 134, 59, 213, 77, 202, 196, 158, 11, 86, 163, 151, 122, 171, 207, 229, 203, 96, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: