← previous blocknext block →recent activity
Analyzing
Block #106,943,994
12 transactions · 12 stateful · 2026-09-22 04:49:10 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,943,994 · 12 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
3w04w15w27w08w29w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f396cee…862f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xeb3f4bff…e791
0x34b655…2a6f
6 touches
3 conflicts
0xd9a74048…63af
0x34b655…2a6f
6 touches
3 conflicts
0x66cc1603…a103
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x6b3ef962…271e
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
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 0x1f396cee30…ac862f
Audit this contract →
← previous block·next block →recent activity