← previous blocknext block →recent activity
Analyzing
Block #105,582,738
27 transactions · 26 stateful · 2026-09-17 10:34:26 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,582,738 · 27 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
5w06w09w110w111w212w313w418w019w125w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08d2198a…629d
0x34b655…2a6f
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x3d8707da…89d1
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0x08d2198a71…2e629d
Audit this contract →
← previous block·next block →recent activity