pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,226,222
← previous block
next block →
recent activity
Analyzing
Block #90,226,222
9 transactions · 8 stateful · 2026-07-25 14:29:19 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,226,222
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updatePosition
#4
0x0f6795d9
· blocks 2
#7
0x6a64c8b7
#8
setData
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5a0a2b03…ac50
0x34b655…2a6f
4 touches
1 conflict
0xd18e4cb7…88d4
0x34b655…2a6f
4 touches
1 conflict
0x3ed31132…62b6
0x34b655…2a6f
4 touches
1 conflict
0x09fcd85c…5069
0x6657d1…8ccc
2 touches
0 conflicts
0x0bc7b670…6a40
0x6657d1…8ccc
2 touches
0 conflicts
0x0bcd7edc…0fdf
0x6657d1…8ccc
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity