Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0857551b79fdd8b96d05c7bd63386b3c079fb35bc4ea3e77e60716de0a1957

Tx prefix hash: 9a0fee08374fbafc5a96b8eacd4912c7f1b03a265039858afc9f2f0cef7f8012
Tx public key: af77c029c3f8087b33213fa5989b1a4f0e2cbd1637d58a64a887c3e94905b694
Timestamp: 1767041266 Timestamp [UTC]: 2025-12-29 20:47:46 Age [y:d:h:m:s]: 00:325:18:24:51
Block: 1444411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238368 RingCT/type: yes/0
Extra: 01af77c029c3f8087b33213fa5989b1a4f0e2cbd1637d58a64a887c3e94905b69402110000000434af31cc000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f61e269fd50aa7a6738f707f027a3f8153433f169ae07404b84fde6d8589e166 0.000600000000 1933325 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": 1444421, "vin": [ { "gen": { "height": 1444411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f61e269fd50aa7a6738f707f027a3f8153433f169ae07404b84fde6d8589e166" } } ], "extra": [ 1, 175, 119, 192, 41, 195, 248, 8, 123, 51, 33, 63, 165, 152, 155, 26, 79, 14, 44, 189, 22, 55, 213, 138, 100, 168, 135, 195, 233, 73, 5, 182, 148, 2, 17, 0, 0, 0, 4, 52, 175, 49, 204, 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: