← previous blocknext block →recent activity
Analyzing
Block #92,356,306
13 transactions · 11 stateful · 2026-08-02 01:22:53 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,356,306 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a2902c…b23f
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xb0d08f6e…b31b
0x34b655…2a6f
4 touches
1 conflict
0xc303beec…ee29
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x55898fed…c787
0x34b655…2a6f
2 touches
0 conflicts
0x5abb42a7…8507
0x34b655…2a6f
2 touches
0 conflicts
0x5eac44da…0868
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
3 conflicts on slot 0x68a2902c52…e3b23f
Audit this contract →
← previous block·next block →recent activity