Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f30dfd8e66f0a1516521c9fccf262bcf6fbc919be29d87fc398638c84163f55

Tx prefix hash: ed79a870f8142ae9280aac241282e3a3b73fe48215c7cc4b66660d4f7385b73a
Tx public key: 038d7d5a192377535a6850f27d746b11aa1bb93281340041060d65fa630fbb36
Timestamp: 1747994724 Timestamp [UTC]: 2025-05-23 10:05:24 Age [y:d:h:m:s]: 01:179:21:52:41
Block: 1289112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392628 RingCT/type: yes/0
Extra: 01038d7d5a192377535a6850f27d746b11aa1bb93281340041060d65fa630fbb360211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0f14bbc1274f5ec86e67684f116ab0cfddc04fcbe9be1b55ea57bc0e0028f20f 0.000600000000 1776579 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": 1289122, "vin": [ { "gen": { "height": 1289112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f14bbc1274f5ec86e67684f116ab0cfddc04fcbe9be1b55ea57bc0e0028f20f" } } ], "extra": [ 1, 3, 141, 125, 90, 25, 35, 119, 83, 90, 104, 80, 242, 125, 116, 107, 17, 170, 27, 185, 50, 129, 52, 0, 65, 6, 13, 101, 250, 99, 15, 187, 54, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: