← previous blocknext block →recent activity
Analyzing
Block #90,300,264
20 transactions · 17 stateful · 2026-07-25 20:43:40 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,300,264 · 20 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
1w04w05w17w08w111w012w213w314w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99137b93…c390
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77b63274…4c9a
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1a1df941…41d5
0x34b655…2a6f
4 touches
1 conflict
0x211c747b…db9b
0x34b655…2a6f
4 touches
1 conflict
0x6ab2c316…2070
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 0x99137b9343…79c390
Audit this contract →
← previous block·next block →recent activity