← previous blocknext block →recent activity
Analyzing
Block #106,397,409
20 transactions · 19 stateful · 2026-09-20 06:57:08 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,397,409 · 20 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
1w02w03w14w28w09w111w312w414w115w516w618w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94a4bafa…58be
0x34b655…2a6f
16 touches
28 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
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 0x94a4bafa99…7958be
Audit this contract →
← previous block·next block →recent activity