pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,676,132
← previous block
next block →
recent activity
Analyzing
Block #75,676,132
6 transactions · 5 stateful · 2026-05-19 19:32:15 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,676,132
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1a945f9c
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#2
0xd10227eb
· blocks 1
#3
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eff5416…605d
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x9f0eb83e…6daf
0xfd44b3…00d1
4 touches
1 conflict
0x749437cf…2fc0
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc1
0x2880ab…7b43
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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:
0xea1b8e4a…8fc5ec
1 conflict on slot
0x6eff5416ed…f5605d
Audit this contract →
← previous block
·
next block →
recent activity