← previous blocknext block →recent activity
Analyzing
Block #92,272,283
39 transactions · 32 stateful · 2026-08-01 18:20:20 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,272,283 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w18w29w311w012w113w015w018w119w420w521w022w123w227w128w229w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7eb441f4…271a
0xa6afd3…d132
8 touches
6 conflicts
0x8fa9bc45…e08f
0xa6afd3…d132
8 touches
6 conflicts
0x45ccb796…428e
0x34b655…2a6f
6 touches
3 conflicts
0x4ff5ffda…05aa
0x34b655…2a6f
6 touches
3 conflicts
0x96d31219…1043
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity