← previous blocknext block →recent activity
Analyzing
Block #100,160,243
11 transactions · 11 stateful · 2026-08-29 10:27:15 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,160,243 · 11 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
2w03w04w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250972e8…5f84
0x34b655…2a6f
4 touches
1 conflict
0x88d8adc5…6fe5
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0x03fe6234…08de
0x34b655…2a6f
2 touches
0 conflicts
0x45b2c12c…deab
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
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 0x250972e8c2…445f84
Audit this contract →
← previous block·next block →recent activity