← previous blocknext block →recent activity
Analyzing
Block #91,209,723
15 transactions · 13 stateful · 2026-07-29 01:12:58 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,209,723 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w28w39w210w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb47f5a…2f8e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x6925548b…81cc
0x34b655…2a6f
4 touches
1 conflict
0x69e67e55…b64e
0x34b655…2a6f
4 touches
1 conflict
0x705ab4ae…0162
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 0xdbb47f5a94…642f8e
Audit this contract →
← previous block·next block →recent activity