pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,473,912
← previous block
next block →
recent activity
Analyzing
Block #93,473,912
9 transactions · 9 stateful · 2026-08-05 23:06:26 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,473,912
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
#2
0x5acec890
#3
0x0f6795d9
· blocks 2
#6
setData
#7
0x39435dac
#8
0x59558d29
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc9cd8eb0…09af
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x4870425f…307f
0x34b655…2a6f
4 touches
1 conflict
0x6f0dfffd…fb74
0x34b655…2a6f
4 touches
1 conflict
0x8d0bf05b…f4da
0x34b655…2a6f
4 touches
1 conflict
0x8eb21bd9…aa8b
0x34b655…2a6f
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity