← previous blocknext block →recent activity
Analyzing
Block #91,153,069
16 transactions · 16 stateful · 2026-07-28 20:28:01 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,153,069 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w39w410w412w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0xfbcd1a83…7b19
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x99bcec21…d6a7
0x34b655…2a6f
6 touches
3 conflicts
0xac388ba5…a800
0x34b655…2a6f
6 touches
3 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x41d7e149…baec
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity