← previous blocknext block →recent activity
Analyzing
Block #92,371,521
30 transactions · 28 stateful · 2026-08-02 02:39:25 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,371,521 · 30 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
1w02w13w24w35w06w17w28w39w311w412w314w515w620w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2ca9bf2…8da8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
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
10 conflicts on slot 0xe2ca9bf21a…2c8da8
Audit this contract →
← previous block·next block →recent activity