← previous blocknext block →recent activity
Analyzing
Block #91,295,467
15 transactions · 13 stateful · 2026-07-29 08:25:12 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,295,467 · 15 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
1w02w04w05w16w07w110w211w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20cb8909…c6c3
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0x465ef31f…1ed7
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0x20cb89092c…8ec6c3
Audit this contract →
← previous block·next block →recent activity