pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,555,755
← previous block
next block →
recent activity
Analyzing
Block #93,555,755
11 transactions · 9 stateful · 2026-08-06 05:57:51 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,555,755
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
0x39435dac
#3
0x0f6795d9
#4
0x0f6795d9
#5
0xb2d4797b
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#6
0x915df74d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x31fd9aa9…e0fc
0x34b655…2a6f
2 touches
0 conflicts
0x3d0a1339…f545
0x34b655…2a6f
2 touches
0 conflicts
0x465ea0dc…23cb
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8def
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:
0x91855e79…58ac7e
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity