← previous blocknext block →recent activity
Analyzing
Block #92,357,281
7 transactions · 7 stateful · 2026-08-02 01:27:48 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,357,281 · 7 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae0f3fcb…fcfd
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0aab3af3…e8f4
0x34b655…2a6f
2 touches
0 conflicts
0x1334d19d…ffcc
0x34b655…2a6f
2 touches
0 conflicts
0x363a4317…87d2
0x34b655…2a6f
2 touches
0 conflicts
0x4b7852de…8cf8
0x34b655…2a6f
2 touches
0 conflicts
0x508bbf1b…fe95
0x34b655…2a6f
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 0xae0f3fcbde…0bfcfd
Audit this contract →
← previous block·next block →recent activity