← previous blocknext block →recent activity
Analyzing
Block #100,849,508
23 transactions · 20 stateful · 2026-08-31 20:19:13 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,849,508 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w110w514w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x295780b7…d2d1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0x59216c5d…f875
0x34b655…2a6f
6 touches
3 conflicts
0x68dfc6ca…56ac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x295780b76d…6dd2d1
Audit this contract →
← previous block·next block →recent activity