Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7134a3c375cf915c66e4584f8ba5dce685e891a2fa87f09b09237e07ca35baac

Tx prefix hash: 91a704c260e6cd1d1729f4977d570d04e3b97b464ddd6b6888eb5eccb1186fbc
Tx public key: 11608430e280f66d221aa7be8b2b5690fb234f5561f10fa91666662cceac4d3d
Timestamp: 1785403460 Timestamp [UTC]: 2026-07-30 09:24:20 Age [y:d:h:m:s]: 00:105:22:36:25
Block: 1601663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 75586 RingCT/type: yes/0
Extra: 0111608430e280f66d221aa7be8b2b5690fb234f5561f10fa91666662cceac4d3d0208d57c6310249aa2c3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a23acc1d197c3b274f7fda7394d74d7a92cecbb8f6d47fa3b8a620fdd73ebf0b 0.000600000000 2091681 of 15 <58>

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": 1601673, "vin": [ { "gen": { "height": 1601663 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a23acc1d197c3b274f7fda7394d74d7a92cecbb8f6d47fa3b8a620fdd73ebf0b", "view_tag": "58" } } } ], "extra": [ 1, 17, 96, 132, 48, 226, 128, 246, 109, 34, 26, 167, 190, 139, 43, 86, 144, 251, 35, 79, 85, 97, 241, 15, 169, 22, 102, 102, 44, 206, 172, 77, 61, 2, 8, 213, 124, 99, 16, 36, 154, 162, 195 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: