← previous blocknext block →recent activity
Analyzing
Block #91,074,293
22 transactions · 19 stateful · 2026-07-28 13:51:37 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,074,293 · 22 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
2w03w14w05w17w08w19w212w213w314w418w319w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ea8cfe…b5c7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50afedcd…91cc
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 0x77ea8cfee7…38b5c7
Audit this contract →
← previous block·next block →recent activity