pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,573,055
← previous block
next block →
recent activity
Analyzing
Block #93,573,055
12 transactions · 11 stateful · 2026-08-06 07:24:49 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,573,055
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
· blocks 1
#5
updatePrices
#6
0x0f6795d9
· blocks 1
#7
batchUpdate
#9
transfer
#10
setData
#11
0x39435dac
#2
matchOrders
#4
0xab083028
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc3de0b…e501
0x99c7a7…8bf0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
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
0x419fa3ec…08ba
0x8f415d…5241
3 touches
1 conflict
0x8454e259…1300
0x99c7a7…8bf0
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xffc3de0b78…59e501
Audit this contract →
← previous block
·
next block →
recent activity