← previous blocknext block →recent activity
Analyzing
Block #106,533,848
25 transactions · 22 stateful · 2026-09-20 18:23:52 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,533,848 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w29w010w112w213w314w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0xa2ad2396…c068
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xd193364c…cd91
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x51799411…9ca7
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
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
10 conflicts on slot 0xe283e878f8…797262
Audit this contract →
← previous block·next block →recent activity