pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,345,198
← previous block
next block →
recent activity
Analyzing
Block #93,345,198
11 transactions · 10 stateful · 2026-08-05 12:19:18 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,345,198
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa2b27c…137b
#2
updatePrices
#3
0x928e4afa
· blocks 1
#4
0x39435dac
#5
0x3f5c179b
#6
0x0f6795d9
#7
setData
#9
0x59558d29
#10
0xc7e3ec2c
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a76de9e…e4b6
0x34b655…2a6f
2 touches
0 conflicts
0x144c76c8…8bb4
0x34b655…2a6f
2 touches
0 conflicts
0x332c1bfe…3b97
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x895c2891…d873
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
0x8fe37a3f4a…bf4c89
Audit this contract →
← previous block
·
next block →
recent activity