← previous blocknext block →recent activity
Analyzing
Block #92,767,329
10 transactions · 9 stateful · 2026-08-03 11:51:18 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,767,329 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7e3a69f…902f
0x34b655…2a6f
4 touches
1 conflict
0xdbd9d618…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x171ff85b…255e
0x34b655…2a6f
4 touches
1 conflict
0x53174844…22f0
0x34b655…2a6f
4 touches
1 conflict
0x57b3b97e…7ca7
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
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
1 conflict on slot 0xf7e3a69f15…9e902f
Audit this contract →
← previous block·next block →recent activity