← previous blocknext block →recent activity
Analyzing
Block #106,383,281
24 transactions · 23 stateful · 2026-09-20 05:46:02 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,383,281 · 24 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
5w07w08w19w216w020w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xc851e4c6…f872
0x34b655…2a6f
4 touches
1 conflict
0xcd9ba26b…108d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a395a6e…8fb9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x7506443aa0…344820
Audit this contract →
← previous block·next block →recent activity