← previous blocknext block →recent activity
Analyzing
Block #91,073,318
14 transactions · 13 stateful · 2026-07-28 13:46:43 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,073,318 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca5c0ac1…62a5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x08a39015…efa0
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50e
0x34b655…2a6f
4 touches
1 conflict
0x252771a6…3918
0x34b655…2a6f
4 touches
1 conflict
0x2595340f…6489
0x34b655…2a6f
4 touches
1 conflict
0x2a310272…5478
0x34b655…2a6f
4 touches
1 conflict
0x334dbb28…1ac2
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 0xca5c0ac1d5…a962a5
Audit this contract →
← previous block·next block →recent activity