pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,836,136
← previous block
next block →
recent activity
Analyzing
Block #90,836,136
8 transactions · 8 stateful · 2026-07-27 17:52:40 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,836,136
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#5
setData
#6
0x39435dac
#7
postPrice
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0xa63bd706…2da7
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x06e6ff87…e712
0x34b655…2a6f
2 touches
0 conflicts
0x06ff9bd7…3f27
0x34b655…2a6f
2 touches
0 conflicts
0x4c7c8c7f…d6fa
0x34b655…2a6f
2 touches
0 conflicts
0x6536722f…6b4e
0x34b655…2a6f
2 touches
0 conflicts
0x67a56c8b…f955
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
0x2bfb71b55d…123a04
Audit this contract →
← previous block
·
next block →
recent activity