← previous blocknext block →recent activity
Analyzing
Block #90,208,283
9 transactions · 8 stateful · 2026-07-25 12:58:53 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,208,283 · 9 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
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
2 touches
0 conflicts
0x77d99233…7634
0x34b655…2a6f
2 touches
0 conflicts
0x8b8499e3…fc0e
0x3aa3d8…0227
2 touches
0 conflicts
0x7f58a1d1…c5a0
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0008
0x4546e6…0f7b
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity