← previous blocknext block →recent activity
Analyzing
Block #106,954,431
30 transactions · 26 stateful · 2026-09-22 05:41:43 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,954,431 · 30 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
2w04w06w08w110w211w314w215w318w020w121w427w128w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01ad5dd0…11a1
0x34b655…2a6f
8 touches
6 conflicts
0xe451d223…2da9
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x9378dce0…3b99
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x94dabb65…43a3
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 0x01ad5dd035…5d11a1
Audit this contract →
← previous block·next block →recent activity