← previous blocknext block →recent activity
Analyzing
Block #105,460,917
57 transactions · 50 stateful · 2026-09-17 00:21:21 UTC
Parallelism
70/100
Blocked
62%
Avg conflicts / tx
2.54
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,460,917 · 57 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w19w010w111w212w114w218w219w320w421w522w623w724w826w927w1028w1129w1236w237w346w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0x2b5101ac…090b
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x2be09ff3…ce49
0x34b655…2a6f
12 touches
15 conflicts
0x48717abe…be13
0x34b655…2a6f
12 touches
15 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
12 touches
15 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
12 touches
15 conflicts
0x5f57e7ab…9f8d
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity