← previous blocknext block →recent activity
Analyzing
Block #90,645,266
13 transactions · 13 stateful · 2026-07-27 01:52:21 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,645,266 · 13 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
1w02w14w05w16w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eb536c7…fa5a
0x7b9256…1fb2
6 touches
3 conflicts
0x0eb536c7…fa57
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x0eb536c7…fa56
0x7b9256…1fb2
6 touches
3 conflicts
0x6ef17495…2359
0x7b9256…1fb2
6 touches
3 conflicts
0x6ef17495…2358
0x7b9256…1fb2
6 touches
3 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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x0eb536c710…c9fa5a
Audit this contract →
← previous block·next block →recent activity