← previous blocknext block →recent activity
Analyzing
Block #90,540,971
6 transactions · 5 stateful · 2026-07-26 17:07:40 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,540,971 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x9737fb40…d8cb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09a168cc…dcc0
0x34b655…2a6f
2 touches
0 conflicts
0x17780e5b…4d01
0x34b655…2a6f
2 touches
0 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0x2f68ff96…38a6
0x34b655…2a6f
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 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity