← previous blocknext block →recent activity
Analyzing
Block #91,063,849
12 transactions · 12 stateful · 2026-07-28 12:59:05 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,063,849 · 12 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
2w04w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a66fa7…9014
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x15c22181…1354
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xb67ae1e1…3728
0x065c9d…c394
2 touches
0 conflicts
0xb9916148…ad81
0x065c9d…c394
2 touches
0 conflicts
0xc4594eb3…d5c5
0x065c9d…c394
2 touches
0 conflicts
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 0x90a66fa7d4…cf9014
Audit this contract →
← previous block·next block →recent activity