← previous blocknext block →recent activity
Analyzing
Block #106,404,536
22 transactions · 21 stateful · 2026-09-20 07:33:00 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.55
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,404,536 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w18w29w210w312w413w514w515w616w717w818w919w1021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
20 touches
45 conflicts
0xe0debfa5…c63e
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xcc9bc5e3…f916
0x34b655…2a6f
10 touches
10 conflicts
0x9ce9a299…afd1
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
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
45 conflicts on slot 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity