Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7cd50aa61646e773fe4c30f704f4832f67ebed9377a28aab503ccabfe6b25b7

Tx prefix hash: eff900c146efdb181d659cf5cf842aa3385b8076da6ce17eeb6a9412244c68ae
Tx public key: 031a4ed7fd9b55646ed65ef983718c8ecc57326eb08959ed5511abbf75a9b4a9
Timestamp: 1773591428 Timestamp [UTC]: 2026-03-15 16:17:08 Age [y:d:h:m:s]: 00:252:02:43:50
Block: 1498488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185006 RingCT/type: yes/0
Extra: 01031a4ed7fd9b55646ed65ef983718c8ecc57326eb08959ed5511abbf75a9b4a9021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0a9b28f894c83b7765db49b4169372ff733fa889ea88e0d15c3cf6057c42a15 0.000600000000 1988134 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": 1498498, "vin": [ { "gen": { "height": 1498488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a9b28f894c83b7765db49b4169372ff733fa889ea88e0d15c3cf6057c42a15" } } ], "extra": [ 1, 3, 26, 78, 215, 253, 155, 85, 100, 110, 214, 94, 249, 131, 113, 140, 142, 204, 87, 50, 110, 176, 137, 89, 237, 85, 17, 171, 191, 117, 169, 180, 169, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: