← previous blocknext block →recent activity
Analyzing
Block #105,576,208
19 transactions · 18 stateful · 2026-09-17 10:01:34 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,576,208 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w010w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x42f11bc6…a231
0x34b655…2a6f
8 touches
6 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xfffc16c6…4651
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
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 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity