← previous blocknext block →recent activity
Analyzing
Block #91,110,570
10 transactions · 8 stateful · 2026-07-28 16:54:12 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,110,570 · 10 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
3w04w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x4eab080a…d0e6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
2 touches
0 conflicts
0x54526994…55b2
0x34b655…2a6f
2 touches
0 conflicts
0x5c16527f…628c
0x34b655…2a6f
2 touches
0 conflicts
0x76ed8777…1e5f
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 0xcd26fba530…bd21c6
Audit this contract →
← previous block·next block →recent activity