← previous blocknext block →recent activity
Analyzing
Block #105,880,999
50 transactions · 39 stateful · 2026-09-18 11:37:05 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.62
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,880,999 · 50 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w28w09w110w011w112w013w014w115w316w419w221w122w023w129w132w333w235w237w441w543w949w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c83a7b1…e305
0x34b655…2a6f
16 touches
28 conflicts
0xbe11ef64…754d
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xcf71e9af…aaad
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
10 touches
10 conflicts
0xd79c9727…1233
0x34b655…2a6f
10 touches
10 conflicts
0xf8e6479f…f193
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x9c83a7b19e…36e305
Audit this contract →
← previous block·next block →recent activity