← previous blocknext block →recent activity
Analyzing
Block #105,855,612
21 transactions · 20 stateful · 2026-09-18 09:29:19 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,855,612 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w110w111w212w313w414w515w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x31e45f46…ad22
0x34b655…2a6f
10 touches
10 conflicts
0x6262c3fa…bb1d
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0x2c8cdc02…795b
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
15 conflicts on slot 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity