← previous blocknext block →recent activity
Analyzing
Block #106,328,029
15 transactions · 14 stateful · 2026-09-20 01:07:58 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,328,029 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
8 touches
6 conflicts
0xb322d117…905e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd9b57567…1f3e
0x34b655…2a6f
6 touches
3 conflicts
0x1a4b4833…cf01
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x4c572488…35d9
0x34b655…2a6f
4 touches
1 conflict
0x4cff6b80…47a8
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 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity