pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,846,179
← previous block
next block →
recent activity
Analyzing
Block #93,846,179
11 transactions · 10 stateful · 2026-08-07 06:17:53 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,846,179
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0x222d4ad6
#5
0x3f5c179b
· blocks 1
#7
0x29eed2d3
#8
execFwdPositionOps
#9
setData
#10
execOrders
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67e4f554…12a3
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…001c
0x1122a5…6e92
2 touches
0 conflicts
0x36321770…862b
0x1122a5…6e92
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
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:
0x851145ea…9f3f07
1 conflict on slot
0x67e4f554d5…cb12a3
Audit this contract →
← previous block
·
next block →
recent activity