pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,247,437
← previous block
next block →
recent activity
Analyzing
Block #74,247,437
7 transactions · 7 stateful · 2026-05-13 04:23:49 UTC
Parallelism
43
/100
Blocked
43
%
Avg conflicts / tx
0.86
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,247,437
· 7 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
supply
· blocks 3
#5
updateDataFeedsValuesPartial
#6
setData
#2
supply
· blocks 2
#3
supply
· blocks 1
#4
supply
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0036
0x293e2f…13a7
8 touches
6 conflicts
0xc27346d4…90a3
0x9c82eb…cd90
8 touches
6 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06679206…a568
0x293e2f…13a7
2 touches
0 conflicts
0xd33612f0…a788
0x293e2f…13a7
2 touches
0 conflicts
0xf3207f2a…0513
0x293e2f…13a7
2 touches
0 conflicts
0xf7a0cd3f…7c16
0x293e2f…13a7
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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:
0x293e2f01…5113a7
6 conflicts on slot
0x0000000000…000036
Audit this contract →
← previous block
·
next block →
recent activity