← previous blocknext block →recent activity
Analyzing
Block #90,511,012
11 transactions · 11 stateful · 2026-07-26 14:37:00 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,511,012 · 11 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
2w03w14w25w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6629b7f2…c972
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x5e1144e3…ca4e
0x34b655…2a6f
4 touches
1 conflict
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
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 0x6629b7f2ce…09c972
Audit this contract →
← previous block·next block →recent activity