← previous blocknext block →recent activity
Analyzing
Block #90,037,670
11 transactions · 10 stateful · 2026-07-24 22:36:00 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,037,670 · 11 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
4w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eef368f…aa21
0x34b655…2a6f
6 touches
3 conflicts
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x76cfb39e…7002
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
2 touches
0 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
2 touches
0 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
2 touches
0 conflicts
0x5170a218…3a84
0xc8689a…ee79
2 touches
0 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: Perpl
3 conflicts on slot 0x8eef368f1b…01aa21
Audit this contract →
← previous block·next block →recent activity