← previous blocknext block →recent activity
Analyzing
Block #105,846,115
26 transactions · 26 stateful · 2026-09-18 08:41:31 UTC
Parallelism
35/100
Blocked
69%
Avg conflicts / tx
4.92
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,846,115 · 26 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
1w04w15w28w39w410w511w612w713w814w915w1016w1117w1218w1319w1424w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
32 touches
120 conflicts
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x067c87f1…e98a
0x34b655…2a6f
20 touches
45 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0xcd5c0ecb…4b5f
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
120 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity