← previous blocknext block →recent activity
Analyzing
Block #92,276,162
17 transactions · 16 stateful · 2026-08-01 18:39:50 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,276,162 · 17 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
2w03w04w16w07w19w010w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfae7e2e1…c2f9
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x127f67c0…40e1
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x743061ce…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x9cd8080e…b255
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xfae7e2e170…11c2f9
Audit this contract →
← previous block·next block →recent activity