← previous blocknext block →recent activity
Analyzing
Block #94,978,999
17 transactions · 14 stateful · 2026-08-11 05:33:20 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,978,999 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w09w110w012w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c4d9965…6182
0x34b655…2a6f
10 touches
10 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0x07c94816…b666
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x0c4d996568…fb6182
Audit this contract →
← previous block·next block →recent activity