← previous blocknext block →recent activity
Analyzing
Block #106,944,891
13 transactions · 13 stateful · 2026-09-22 04:53:41 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,944,891 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w19w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea2d1275…76c8
0x34b655…2a6f
4 touches
1 conflict
0x01ad5dd0…11a1
0x34b655…2a6f
4 touches
1 conflict
0x3d644650…694f
0x34b655…2a6f
4 touches
1 conflict
0xb77b424a…9a25
0x34b655…2a6f
4 touches
1 conflict
0xb321ac8c…43b1
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
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
3 conflicts on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity