← previous blocknext block →recent activity
Analyzing
Block #91,984,030
19 transactions · 18 stateful · 2026-07-31 18:10:36 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,984,030 · 19 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
3w04w18w09w110w211w312w013w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7e2686d…4438
0x7b9256…1fb2
8 touches
6 conflicts
0xa3d54bdd…a44a
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xa3d54bdd…a448
0x7b9256…1fb2
8 touches
6 conflicts
0xa3d54bdd…a449
0x7b9256…1fb2
8 touches
6 conflicts
0xe7e2686d…443c
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0xe7e2686d36…394438
Audit this contract →
← previous block·next block →recent activity