← previous blocknext block →recent activity
Analyzing
Block #90,043,251
8 transactions · 8 stateful · 2026-07-24 23:04:10 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,043,251 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7aced05…46bd
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x1917862f…5af0
0x34b655…2a6f
4 touches
1 conflict
0x5ccbe540…cb67
0x065c9d…c394
2 touches
0 conflicts
0xc5a0d756…3624
0x065c9d…c394
2 touches
0 conflicts
0xf8d18c38…09be
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0xb7aced0592…9246bd
Audit this contract →
← previous block·next block →recent activity