← previous blocknext block →recent activity
Analyzing
Block #106,456,688
18 transactions · 18 stateful · 2026-09-20 11:55:32 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,456,688 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w212w313w414w515w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a21beda…27eb
0x34b655…2a6f
14 touches
21 conflicts
0x747304c5…ad3e
0x34b655…2a6f
10 touches
10 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xfaee4f79…d6ee
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
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
21 conflicts on slot 0x2a21bedaa8…ac27eb
Audit this contract →
← previous block·next block →recent activity