← previous blocknext block →recent activity
Analyzing
Block #92,447,772
10 transactions · 10 stateful · 2026-08-02 09:02:51 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,447,772 · 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
2w03w15w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ca5d311…286f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x42b04648…21d2
0x34b655…2a6f
2 touches
0 conflicts
0x4e50038e…6e29
0x34b655…2a6f
2 touches
0 conflicts
0x5b3f9959…fede
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 0x5ca5d3118b…5f286f
Audit this contract →
← previous block·next block →recent activity