← previous blocknext block →recent activity
Analyzing
Block #91,159,596
14 transactions · 12 stateful · 2026-07-28 21:00:50 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,159,596 · 14 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
2w03w14w05w17w28w311w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x802738ef…9072
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x162f5e54…ef30
0x34b655…2a6f
4 touches
1 conflict
0x16895b68…4030
0x34b655…2a6f
4 touches
1 conflict
0x29b9d1a4…2c4a
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
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 0x802738ef70…cb9072
Audit this contract →
← previous block·next block →recent activity