← previous blocknext block →recent activity
Analyzing
Block #91,108,735
17 transactions · 16 stateful · 2026-07-28 16:44:59 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,108,735 · 17 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
2w05w16w07w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc561db58…139e
0x7b9256…1fb2
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
0xbfd744bf…c9dd
0x7b9256…1fb2
4 touches
1 conflict
0xbfd744bf…c9de
0x7b9256…1fb2
4 touches
1 conflict
0xc561db58…139a
0x7b9256…1fb2
4 touches
1 conflict
0xc561db58…139b
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 0xc561db581f…5a139e
Audit this contract →
← previous block·next block →recent activity