pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,587,159
14 transactions · 14 stateful · 2026-05-14 18:10:57 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,587,159 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w011w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0xf7a94d77…8319
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x876ddba9…b47f
0xd32edf…ff58
3 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x770f14b6…10ac
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
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: 0xab35264b…1cfa38
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity