← previous blocknext block →recent activity
Analyzing
Block #91,070,630
15 transactions · 14 stateful · 2026-07-28 13:33:12 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,070,630 · 15 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
2w03w04w18w19w211w312w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x2d93071a…5ba7
0x34b655…2a6f
4 touches
1 conflict
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc6f3c5a3…3faa
0x34b655…2a6f
4 touches
1 conflict
0xd4b0bafb…80ac
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 0x0ab54c30a6…82b88e
Audit this contract →
← previous block·next block →recent activity