← previous blocknext block →recent activity
Analyzing
Block #92,049,630
9 transactions · 8 stateful · 2026-07-31 23:40:31 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,049,630 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7e0e69…e6d1
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x6bb86528…5b27
0x34b655…2a6f
3 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x107ec1e0…026d
0x34b655…2a6f
2 touches
0 conflicts
0x20fb35c7…09c2
0x34b655…2a6f
2 touches
0 conflicts
0x75cc4b3f…d680
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 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
1 conflict on slot 0x5d7e0e6938…45e6d1
Audit this contract →
← previous block·next block →recent activity