← previous blocknext block →recent activity
Analyzing
Block #106,100,120
28 transactions · 27 stateful · 2026-09-19 06:00:55 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,100,120 · 28 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
1w02w13w04w15w16w27w09w114w216w117w218w319w320w421w423w525w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7013779…71d5
0x34b655…2a6f
8 touches
6 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
8 touches
6 conflicts
0x41f84c6d…8369
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0xbf8a0ace…7ac7
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xe7013779b8…5671d5
Audit this contract →
← previous block·next block →recent activity