Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8807c449a71ac2f7568b53f6bd04183dbbb5cd84645d68dfa37b1c49165c32b1

Tx prefix hash: a5d4503f5137e94afa112b93c1375a676efbcc4c834d8f68f6cdb97d4a575fdc
Tx public key: d7fa50c765838fc25a825ec08a8dedbfd1d8c93de92dfd28e5f7b39ea52c6309
Timestamp: 1743146906 Timestamp [UTC]: 2025-03-28 07:28:26 Age [y:d:h:m:s]: 01:236:09:11:09
Block: 1248962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433055 RingCT/type: yes/0
Extra: 01d7fa50c765838fc25a825ec08a8dedbfd1d8c93de92dfd28e5f7b39ea52c6309021100000009d2e40efd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 454c1c0eb60073a33b9754c1d2a1125d3dc7fb991f5b9c4fe451d6d9d0b7ca76 0.000600000000 1735997 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": 1248972, "vin": [ { "gen": { "height": 1248962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "454c1c0eb60073a33b9754c1d2a1125d3dc7fb991f5b9c4fe451d6d9d0b7ca76" } } ], "extra": [ 1, 215, 250, 80, 199, 101, 131, 143, 194, 90, 130, 94, 192, 138, 141, 237, 191, 209, 216, 201, 61, 233, 45, 253, 40, 229, 247, 179, 158, 165, 44, 99, 9, 2, 17, 0, 0, 0, 9, 210, 228, 14, 253, 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: