← previous blocknext block →recent activity
Analyzing
Block #105,377,445
24 transactions · 22 stateful · 2026-09-16 17:21:09 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,377,445 · 24 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
9w010w111w212w314w017w118w219w320w422w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc389d1ff…6a00
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x224b3c8d…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0xbbe18325…bd34
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xc389d1ff6d…226a00
Audit this contract →
← previous block·next block →recent activity