← previous blocknext block →recent activity
Analyzing
Block #91,396,233
17 transactions · 16 stateful · 2026-07-29 16:52:18 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,396,233 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w19w010w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62422816…47ed
0x7b9256…1fb2
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x5d71b10a…bb5d
0x7b9256…1fb2
4 touches
1 conflict
0x5d71b10a…bb5e
0x7b9256…1fb2
4 touches
1 conflict
0x5d71b10a…bb61
0x7b9256…1fb2
4 touches
1 conflict
0x62422816…47ec
0x7b9256…1fb2
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x62422816e8…0347ed
Audit this contract →
← previous block·next block →recent activity