pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,802,425
← previous block
next block →
recent activity
Analyzing
Block #90,802,425
9 transactions · 9 stateful · 2026-07-27 15:03:00 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,802,425
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
airdrop
#2
0x532c46db
· blocks 1
#4
0x3f5c179b
#5
0x0f6795d9
· blocks 1
#7
0x6a67739b
#8
setData
#3
0x532c46db
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c93cb32…22e6
0x851145…3f07
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x57b57f51…2449
0x34b655…2a6f
4 touches
1 conflict
0xccdc32f8…72be
0x34b655…2a6f
4 touches
1 conflict
0xd8eed7e0…c96e
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
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:
0x851145ea…9f3f07
1 conflict on slot
0x3c93cb32a4…fa22e6
Audit this contract →
← previous block
·
next block →
recent activity