← previous blocknext block →recent activity
Analyzing
Block #106,207,235
30 transactions · 26 stateful · 2026-09-19 15:00:02 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
1.57
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,207,235 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w28w119w320w423w524w625w726w828w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe53e265c…e468
0x34b655…2a6f
16 touches
28 conflicts
0x65f8fcff…e6ba
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0xe27119e1…dcaa
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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
28 conflicts on slot 0xe53e265c6a…fde468
Audit this contract →
← previous block·next block →recent activity