pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,261,787
15 transactions · 12 stateful · 2026-05-17 21:16:13 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,261,787 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xb68c32d8…86ee
0x065c9d…c394
3 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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: 0x065c9d28…a9c394
1 conflict on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity