← previous blocknext block →recent activity
Analyzing
Block #105,608,211
22 transactions · 22 stateful · 2026-09-17 12:42:39 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,608,211 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w27w28w09w114w315w416w519w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3e108b2…d517
0x34b655…2a6f
10 touches
10 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5202469c…bec0
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
10 conflicts on slot 0xb3e108b23f…e7d517
Audit this contract →
← previous block·next block →recent activity