← previous blocknext block →recent activity
Analyzing
Block #91,079,047
10 transactions · 10 stateful · 2026-07-28 14:15:34 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,079,047 · 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
1w04w05w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e370792…a916
0x7b9256…1fb2
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x5891d42e…580b
0x7b9256…1fb2
4 touches
1 conflict
0x5891d42e…580c
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x5e3707927c…72a916
Audit this contract →
← previous block·next block →recent activity