pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,116,385
← previous block
next block →
recent activity
Analyzing
Block #99,116,385
10 transactions · 10 stateful · 2026-08-25 18:38:48 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,116,385
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
handleOps
· blocks 1
#5
forward
#6
0xed82b078
#7
0x6a8de1b0
#8
setData
#9
execOrders
#4
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x059e0ac0…0267
0x34b655…2a6f
2 touches
0 conflicts
0x55010ec8…ea31
0x34b655…2a6f
2 touches
0 conflicts
0x5dd7e5bb…62dd
0x34b655…2a6f
2 touches
0 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
2 touches
0 conflicts
0x782c1b68…0a37
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:
0x5ff137d4…6d2789
1 conflict on slot
0x33a26eb216…ad2df0
Audit this contract →
← previous block
·
next block →
recent activity