pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,288,718
← previous block
next block →
recent activity
Analyzing
Block #99,288,718
11 transactions · 8 stateful · 2026-08-26 09:06:00 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,288,718
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa5395a…5561
#2
0x73fc90…2aea
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
setData
#7
0x61d59c2d
· blocks 1
#9
execOrders
#10
execOrders
#8
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc9520be…83a3
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ec05
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ec06
0x77d53b…8080
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a0b
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a0c
0x77d53b…8080
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:
0x77d53b3b…378080
1 conflict on slot
0xfc9520be1c…7083a3
Audit this contract →
← previous block
·
next block →
recent activity