← previous blocknext block →recent activity
Analyzing
Block #106,207,925
19 transactions · 19 stateful · 2026-09-19 15:03:31 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,207,925 · 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
2w03w04w15w29w112w113w214w315w416w517w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94f4eab2…673c
0x34b655…2a6f
14 touches
21 conflicts
0xf5330358…1304
0x34b655…2a6f
12 touches
15 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0xebf4a826…a80c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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 0x94f4eab25f…91673c
Audit this contract →
← previous block·next block →recent activity