← previous blocknext block →recent activity
Analyzing
Block #90,441,267
15 transactions · 13 stateful · 2026-07-26 08:45:50 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,441,267 · 15 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
2w03w17w08w110w212w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4930bd3…6af2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd05c5e71…4e6d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0xb7ad72ac…c7a9
0x34b655…2a6f
6 touches
3 conflicts
0x783044a0…9f4e
0x34b655…2a6f
6 touches
3 conflicts
0x8f888556…f387
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 0xc4930bd393…e46af2
Audit this contract →
← previous block·next block →recent activity