Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ee6731ecb1eb2422d1bbd0976a7ee8bd6b1ace20fe038e084996e54070b938

Tx prefix hash: b8afda7e508d7f01a677a91744775b34df5a2660cb1e75ba165e468c550422bb
Tx public key: 931740d0eb29ae1aa789bd47f30fb8786ba6e5f8e9bb87c61ea4919a913645e0
Timestamp: 1762162961 Timestamp [UTC]: 2025-11-03 09:42:41 Age [y:d:h:m:s]: 00:190:17:29:13
Block: 1403979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128571 RingCT/type: yes/0
Extra: 01931740d0eb29ae1aa789bd47f30fb8786ba6e5f8e9bb87c61ea4919a913645e0021100000001df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1768b6ef3cb0fc2f926244f65a9b38b3f9118cea6e89466fab3490061f46a3b 0.000600000000 1892336 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": 1403989, "vin": [ { "gen": { "height": 1403979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1768b6ef3cb0fc2f926244f65a9b38b3f9118cea6e89466fab3490061f46a3b" } } ], "extra": [ 1, 147, 23, 64, 208, 235, 41, 174, 26, 167, 137, 189, 71, 243, 15, 184, 120, 107, 166, 229, 248, 233, 187, 135, 198, 30, 164, 145, 154, 145, 54, 69, 224, 2, 17, 0, 0, 0, 1, 223, 90, 36, 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: