pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,208,918
← previous block
next block →
recent activity
Analyzing
Block #90,208,918
9 transactions · 8 stateful · 2026-07-25 13:02:05 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,208,918
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x5a5d9a99
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f683e34…ca0c
0x34b655…2a6f
4 touches
1 conflict
0x4d1c2806…5947
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0xc3656cd1…8269
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0xe1b2a1f2…d5fc
0x34b655…2a6f
4 touches
1 conflict
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
0x6f683e347e…13ca0c
Audit this contract →
← previous block
·
next block →
recent activity