← previous blocknext block →recent activity
Analyzing
Block #106,933,984
19 transactions · 18 stateful · 2026-09-22 03:58:47 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,933,984 · 19 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
8w09w111w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0x3780a34a…b50a
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
4 touches
1 conflict
0xd67c8391…ded5
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 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
21 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity