pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,472,213
14 transactions · 13 stateful · 2026-05-14 05:19:17 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,472,213 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
2 touches
0 conflicts
0xe8adf936…34b0
0x188d58…ea8e
2 touches
0 conflicts
0xe8adf936…34b1
0x188d58…ea8e
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
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity