pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,504,983
← previous block
next block →
recent activity
Analyzing
Block #93,504,983
11 transactions · 9 stateful · 2026-08-06 01:42:38 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,504,983
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x39435dac
#3
0x5acec890
#4
0x5acec890
#5
0x0f6795d9
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#9
setData
#10
0x59558d29
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0x88413c1a…7783
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:
Perpl
1 conflict on slot
0x91cdfdebc5…487feb
Audit this contract →
← previous block
·
next block →
recent activity