← previous blocknext block →recent activity
Analyzing
Block #98,569,238
25 transactions · 25 stateful · 2026-08-23 20:16:30 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,569,238 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w111w012w113w014w117w018w119w220w321w422w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0008
0x0ea966…0742
10 touches
10 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
10 touches
10 conflicts
0x724cd9ff…6684
0xe4f6e7…9657
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: MONI (MONI)
10 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity