pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,227,915
← previous block
next block →
recent activity
Analyzing
Block #94,227,915
10 transactions · 9 stateful · 2026-08-08 14:22:26 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,227,915
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
0x39435dac
#4
0x0f6795d9
#6
0x0f6795d9
#7
0x0f6795d9
#8
setData
#9
0x39435dac
#2
0x5acec890
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x61b1ca86…dac1
0x34b655…2a6f
4 touches
1 conflict
0x04ed9b8b…16c8
0x34b655…2a6f
2 touches
0 conflicts
0x18de6e82…7ec0
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x3c3621c7…3e11
0x34b655…2a6f
2 touches
0 conflicts
0x3d22c439…de6d
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
0x5502e1cc19…1a3910
Audit this contract →
← previous block
·
next block →
recent activity