← previous blocknext block →recent activity
Analyzing
Block #108,873,623
43 transactions · 31 stateful · 2026-09-28 22:47:20 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
1.93
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #108,873,623 · 43 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w19w010w111w012w114w219w320w221w322w425w526w631w232w333w436w537w638w742w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x801a6e57…d85c
0x34b655…2a6f
12 touches
15 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
12 touches
15 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
10 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity