← previous blocknext block →recent activity
Analyzing
Block #90,513,387
24 transactions · 23 stateful · 2026-07-26 14:48:56 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,513,387 · 24 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
1w02w13w29w010w112w214w215w117w018w119w020w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xacfd8774…87ec
0x34b655…2a6f
8 touches
6 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
8 touches
6 conflicts
0xec0af936…5c04
0x34b655…2a6f
8 touches
6 conflicts
0x03b16972…8f62
0x34b655…2a6f
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x4ac2a863…cba1
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity