pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,903,022
← previous block
next block →
recent activity
Analyzing
Block #94,903,022
8 transactions · 8 stateful · 2026-08-10 23:11:13 UTC
Parallelism
38
/100
Blocked
50
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,903,022
· 8 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
placeAndExecuteMarketSell
· blocks 3
#6
setData
#7
0x59558d29
#2
placeAndExecuteMarketSell
· blocks 2
#3
placeAndExecuteMarketBuy
· blocks 2
#4
placeAndExecuteMarketBuy
· blocks 1
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xb8c9b779…1eb7
0x851145…3f07
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x3c4d4a5d…7c63
0x851145…3f07
4 touches
1 conflict
0x513bcef5…048e
0x01bff4…1071
2 touches
0 conflicts
0x758f26d7…858f
0x01bff4…1071
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:
0x01bff417…bc1071
6 conflicts on slot
0x11b69a7ea1…83334e
Audit this contract →
← previous block
·
next block →
recent activity