← previous blocknext block →recent activity
Analyzing
Block #99,183,661
8 transactions · 8 stateful · 2026-08-26 00:17:22 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,183,661 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x330587fd…4cd7
0x34b655…2a6f
4 touches
1 conflict
0x79347b24…9fba
0x34b655…2a6f
4 touches
1 conflict
0x08f9d5f2…7b92
0x34b655…2a6f
2 touches
0 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
2 touches
0 conflicts
0x3bab2dde…e97f
0x34b655…2a6f
2 touches
0 conflicts
0x41090b5b…98d5
0x34b655…2a6f
2 touches
0 conflicts
0x437c5e1a…8479
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x2c2761c0a9…ff476e
Audit this contract →
← previous block·next block →recent activity