← previous blocknext block →recent activity
Analyzing
Block #91,101,797
18 transactions · 16 stateful · 2026-07-28 16:10:04 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,101,797 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w59w012w413w114w216w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x26333103…38db
0x34b655…2a6f
4 touches
1 conflict
0x32e4c206…a476
0x34b655…2a6f
4 touches
1 conflict
0x5a4d5f09…5094
0x34b655…2a6f
4 touches
1 conflict
0x63b74d88…b6ca
0x34b655…2a6f
4 touches
1 conflict
0x6f988a4a…b39f
0x34b655…2a6f
4 touches
1 conflict
0x701a65bd…3f81
0x34b655…2a6f
4 touches
1 conflict
0x7604a8f8…d63a
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity