← previous blocknext block →recent activity
Analyzing
Block #91,540,768
9 transactions · 8 stateful · 2026-07-30 05:00:45 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,540,768 · 9 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
2w04w15w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79ce2c35…44f4
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x01a056f8…64e4
0x34b655…2a6f
2 touches
0 conflicts
0x0a0ac643…b698
0x34b655…2a6f
2 touches
0 conflicts
0x2f475d04…03fa
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…caca
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
1 conflict on slot 0x79ce2c3539…a044f4
Audit this contract →
← previous block·next block →recent activity