← previous blocknext block →recent activity
Analyzing
Block #91,974,197
16 transactions · 16 stateful · 2026-07-31 17:21:09 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,974,197 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb742d0cd…b9eb
0x7b9256…1fb2
4 touches
1 conflict
0x0c10eea3…e440
0x7b9256…1fb2
4 touches
1 conflict
0x0c10eea3…e441
0x7b9256…1fb2
4 touches
1 conflict
0xb742d0cd…b9e7
0x7b9256…1fb2
4 touches
1 conflict
0xb742d0cd…b9e8
0x7b9256…1fb2
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x7b9256fd…e21fb2
1 conflict on slot 0xb742d0cd62…48b9eb
Audit this contract →
← previous block·next block →recent activity