pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,551,832
← previous block
next block →
recent activity
Analyzing
Block #90,551,832
8 transactions · 8 stateful · 2026-07-26 18:02:18 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,551,832
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x0f6795d9
· blocks 2
#5
0x3f5c179b
#6
0x6a664c22
#7
setData
#3
0x0f6795d9
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2894b5dd…5c2e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xe624cb16…9dc0
0x34b655…2a6f
4 touches
1 conflict
0x1294a92c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x32d8a305…96ee
0x34b655…2a6f
2 touches
0 conflicts
0x3f50773b…47ef
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity