pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,889,950
← previous block
next block →
recent activity
Analyzing
Block #90,889,950
8 transactions · 8 stateful · 2026-07-27 22:23:24 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,889,950
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x3f5c179b
#4
setData
#5
0x39435dac
· blocks 1
#7
0xc7e3ec2c
#3
0x0f6795d9
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00dcbc22…8053
0x34b655…2a6f
2 touches
0 conflicts
0x02693e83…54be
0x34b655…2a6f
2 touches
0 conflicts
0x096e297f…64b4
0x34b655…2a6f
2 touches
0 conflicts
0x0d4b170b…8f0e
0x34b655…2a6f
2 touches
0 conflicts
0x143bcba4…162e
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
0x1ebb35bbe9…41ef2a
Audit this contract →
← previous block
·
next block →
recent activity