← previous blocknext block →recent activity
Analyzing
Block #106,456,702
23 transactions · 20 stateful · 2026-09-20 11:55:36 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,456,702 · 23 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
1w02w03w15w17w29w212w214w316w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33365a6a…7e0b
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x10529837…b6b4
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
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
15 conflicts on slot 0x33365a6a88…d17e0b
Audit this contract →
← previous block·next block →recent activity