Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104d26da8b39c6f8ad41d7abe5d75b91e4cd048721f4ccd3665745b98984b41d

Tx prefix hash: 230a96ad193d2e22c81da7d2f6133ae111af2f95ee07e74bd5b784b537fe338f
Tx public key: a891081abefd7b5208d986c7fd8313f040fb014379648ea3dd95b018a8d379fb
Timestamp: 1743278303 Timestamp [UTC]: 2025-03-29 19:58:23 Age [y:d:h:m:s]: 01:235:23:35:39
Block: 1250057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432841 RingCT/type: yes/0
Extra: 01a891081abefd7b5208d986c7fd8313f040fb014379648ea3dd95b018a8d379fb0211000000021a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb108d597d8c6b233a800051ffe513fe12a6211c91e74d02124a7d8ba91ffd82 0.000600000000 1737104 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": 1250067, "vin": [ { "gen": { "height": 1250057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb108d597d8c6b233a800051ffe513fe12a6211c91e74d02124a7d8ba91ffd82" } } ], "extra": [ 1, 168, 145, 8, 26, 190, 253, 123, 82, 8, 217, 134, 199, 253, 131, 19, 240, 64, 251, 1, 67, 121, 100, 142, 163, 221, 149, 176, 24, 168, 211, 121, 251, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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: