← previous blocknext block →recent activity
Analyzing
Block #92,276,034
21 transactions · 16 stateful · 2026-08-01 18:39:12 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,276,034 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w09w110w011w113w214w115w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x1d86f412…d0b5
0xa6afd3…d132
4 touches
1 conflict
0xf0bf41b6…682f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x127f67c0…40e1
0x34b655…2a6f
4 touches
1 conflict
0x743061ce…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x76274dfc…36fa
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 0xda27c76455…2e7fab
Audit this contract →
← previous block·next block →recent activity