pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,937,816
← previous block
next block →
recent activity
Analyzing
Block #99,937,816
12 transactions · 12 stateful · 2026-08-28 15:47:05 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,937,816
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
updatePrices
· blocks 1
#5
0xab083028
· blocks 1
#6
0x59558d29
#8
execFwdPositionOpsV2
#9
0xed82b078
#10
0xed82b078
#11
execOrders
#4
updatePrices
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c1b3e4…4865
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xf1a7680f…af73
0x40c49f…2af0
3 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x56bda32b…b310
0x065c9d…c394
2 touches
0 conflicts
0x739ab388…e377
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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
0xa0c1b3e492…e24865
Audit this contract →
← previous block
·
next block →
recent activity