← previous blocknext block →recent activity
Analyzing
Block #108,533,815
25 transactions · 25 stateful · 2026-09-27 18:13:30 UTC
Parallelism
36/100
Blocked
72%
Avg conflicts / tx
4.44
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #108,533,815 · 25 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w38w410w511w612w713w814w915w1016w1117w1218w1319w1420w1523w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
28 touches
91 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
28 touches
91 conflicts
0x0ddc998e…def8
0x34b655…2a6f
26 touches
78 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
26 touches
78 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
26 touches
78 conflicts
0x5969523e…5191
0x34b655…2a6f
26 touches
78 conflicts
0x787b5cb5…e76a
0x34b655…2a6f
26 touches
78 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
26 touches
78 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
91 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity