← previous blocknext block →recent activity
Analyzing
Block #106,934,442
23 transactions · 21 stateful · 2026-09-22 04:01:05 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,934,442 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w09w110w211w312w113w214w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x13ef7024…9966
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3d4ceda4…84c4
0x34b655…2a6f
4 touches
1 conflict
0xa0edadb9…dbfe
0x34b655…2a6f
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
6 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity