← previous blocknext block →recent activity
Analyzing
Block #91,065,463
10 transactions · 9 stateful · 2026-07-28 13:07:12 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,065,463 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x4c1163be…cdc5
0x34b655…2a6f
4 touches
1 conflict
0x67ab38cc…c8b9
0x34b655…2a6f
4 touches
1 conflict
0x8dd2ae5f…b8dd
0x34b655…2a6f
4 touches
1 conflict
0x9430a4d7…1f35
0x34b655…2a6f
4 touches
1 conflict
0xabba7bd6…8269
0x34b655…2a6f
4 touches
1 conflict
0xabba7bd6…826a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity