pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,067,819
← previous block
next block →
recent activity
Analyzing
Block #90,067,819
8 transactions · 8 stateful · 2026-07-25 01:08:32 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,067,819
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 2
#2
0x0f6795d9
#3
0x3f5c179b
#5
setData
#7
0xc7e3ec2c
#4
0x39435dac
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xe8d8a9a2…40f3
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
0x34b655…2a6f
2 touches
0 conflicts
0x3ac09fce…bb39
0x34b655…2a6f
2 touches
0 conflicts
0x5d77346a…863a
0x34b655…2a6f
2 touches
0 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
2 touches
0 conflicts
0x5f56ffe5…09c0
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity