pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,626,422
← previous block
next block →
recent activity
Analyzing
Block #90,626,422
8 transactions · 7 stateful · 2026-07-27 00:17:33 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,626,422
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
#2
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
0x6a66a414
#6
setData
#7
0x8d17eb…0a0b
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x282f129e…8f33
0x34b655…2a6f
4 touches
1 conflict
0x7fa88ae3…cf7c
0x34b655…2a6f
4 touches
1 conflict
0x82bfe0c3…49c9
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x0a6ba3b4…2123
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da89
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da8a
0x34b655…2a6f
2 touches
0 conflicts
0x3b1ce1dd…dc2f
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
0x282f129ecc…2b8f33
Audit this contract →
← previous block
·
next block →
recent activity