← previous blocknext block →recent activity
Analyzing
Block #90,037,081
10 transactions · 10 stateful · 2026-07-24 22:33:02 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,037,081 · 10 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
1w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e246445…9e0e
0x34b655…2a6f
4 touches
1 conflict
0xc7277122…8339
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe999cbf5…d18a
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x2e925763…0a21
0x34b655…2a6f
2 touches
0 conflicts
0x375d97e8…4d4f
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
0x34b655…2a6f
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
1 conflict on slot 0x0e2464459c…149e0e
Audit this contract →
← previous block·next block →recent activity