← previous blocknext block →recent activity
Analyzing
Block #98,678,090
23 transactions · 20 stateful · 2026-08-24 05:43:28 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,678,090 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w19w010w111w016w217w018w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cef1eff…9f14
0x34b655…2a6f
6 touches
3 conflicts
0x0bd5c557…de1e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a6
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a7
0x34b655…2a6f
4 touches
1 conflict
0x698d8b5e…1fc8
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x2cef1eff78…339f14
Audit this contract →
← previous block·next block →recent activity