pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,626,766
← previous block
next block →
recent activity
Analyzing
Block #90,626,766
10 transactions · 10 stateful · 2026-07-27 00:19:17 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,626,766
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0x0f6795d9
· blocks 1
#4
0x5339c59f
· blocks 1
#7
0xed82b078
#8
setData
#9
0x39435dac
#2
swap
#5
0x3f5c179b
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd170a8d4…eb9a
0x99ae2d…8888
2 touches
1 conflict
0x00000000…0008
0x301102…b74c
2 touches
0 conflicts
0x0c376bba…95b1
0x34b655…2a6f
2 touches
0 conflicts
0x2d8487d0…24c6
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
0xe8d58d3462…c2426d
Audit this contract →
← previous block
·
next block →
recent activity