← previous blocknext block →recent activity
Analyzing
Block #91,161,724
12 transactions · 12 stateful · 2026-07-28 21:11:32 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,161,724 · 12 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
2w05w18w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4ff6e8d…0427
0x34b655…2a6f
4 touches
1 conflict
0x91ace65b…97af
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0802d0d8…dd0c
0x34b655…2a6f
4 touches
1 conflict
0x1346ac01…31f2
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
1 conflict on slot 0xf4ff6e8d47…8f0427
Audit this contract →
← previous block·next block →recent activity