← previous blocknext block →recent activity
Analyzing
Block #106,200,201
22 transactions · 21 stateful · 2026-09-19 14:24:35 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,200,201 · 22 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
1w03w05w06w17w29w110w213w117w318w419w520w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
12 touches
15 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
10 touches
10 conflicts
0x253561ba…8c1a
0x34b655…2a6f
10 touches
10 conflicts
0xf1564b2b…970b
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
6 touches
3 conflicts
0x7f0725e9…66f7
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity