pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,345,119
← previous block
next block →
recent activity
Analyzing
Block #92,345,119
9 transactions · 9 stateful · 2026-08-02 00:26:38 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,345,119
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7c51d6cf
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
0xed82b078
#6
0x6a6e8f36
#7
setData
#8
0xc7e3ec2c
#2
0x7c51d6cf
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8ba5330…4d44
0x40c49f…2af0
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x0287e69c…74b4
0x34b655…2a6f
2 touches
0 conflicts
0x08b8fc29…a90b
0x34b655…2a6f
2 touches
0 conflicts
0x0f1cb25b…2764
0x34b655…2a6f
2 touches
0 conflicts
0x167ca698…e836
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:
0x40c49f17…d22af0
1 conflict on slot
0xb8ba533027…244d44
Audit this contract →
← previous block
·
next block →
recent activity