← previous blocknext block →recent activity
Analyzing
Block #98,983,240
17 transactions · 16 stateful · 2026-08-25 07:22:19 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,983,240 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w09w110w111w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf0302cb…e4d8
0x8964d7…10f8
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbf0302cb…e4d1
0x8964d7…10f8
6 touches
3 conflicts
0xbf0302cb…e4d2
0x8964d7…10f8
6 touches
3 conflicts
0xbf0302cb…e4d5
0x8964d7…10f8
6 touches
3 conflicts
0xefb236ca…f49b
0x34b655…2a6f
6 touches
3 conflicts
0xbf0302cb…e4d6
0x8964d7…10f8
6 touches
3 conflicts
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xbf0302cbc8…8be4d8
Audit this contract →
← previous block·next block →recent activity