← previous blocknext block →recent activity
Analyzing
Block #105,583,290
11 transactions · 11 stateful · 2026-09-17 10:37:12 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,583,290 · 11 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
1w02w13w05w06w17w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b816c…a5e0
0x34b655…2a6f
6 touches
3 conflicts
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0x3c6888af…a179
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x932fc4ea…4b1d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
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
3 conflicts on slot 0x213b816cc7…d4a5e0
Audit this contract →
← previous block·next block →recent activity