← previous blocknext block →recent activity
Analyzing
Block #94,812,427
36 transactions · 30 stateful · 2026-08-10 15:35:31 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,812,427 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w29w010w112w013w114w215w016w120w222w425w326w427w528w229w130w332w334w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7083b83e…33da
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xfecb18c068…6e01ed
Audit this contract →
← previous block·next block →recent activity