pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,499,923
← previous block
next block →
recent activity
Analyzing
Block #93,499,923
10 transactions · 10 stateful · 2026-08-06 01:17:12 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,499,923
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x0f6795d9
· blocks 2
#5
0x532c46db
#8
updateDataFeedsValuesPartial
#9
setData
#2
matchOrders
#6
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb716420…9b5b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x29ba534c…fe06
0x754704…b603
4 touches
1 conflict
0x303ace4f…eae8
0x754704…b603
4 touches
1 conflict
0x9ed41050…1125
0x99c7a7…8bf0
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:
Perpl
3 conflicts on slot
0xbb716420d8…629b5b
Audit this contract →
← previous block
·
next block →
recent activity