← previous blocknext block →recent activity
Analyzing
Block #90,693,951
15 transactions · 13 stateful · 2026-07-27 05:57:16 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,693,951 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w210w012w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7b9c56…69cf
0x34b655…2a6f
6 touches
3 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
0x4e37574f…4145
0x34b655…2a6f
4 touches
1 conflict
0x59e54d3e…4c85
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x007892de…5752
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: Perpl
3 conflicts on slot 0x7b7b9c5673…f669cf
Audit this contract →
← previous block·next block →recent activity