pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,463,689
17 transactions · 11 stateful · 2026-05-14 04:22:41 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,463,689 · 17 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
1w02w03w16w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xc495db78…3873
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x78b7bb99…b926
0x0594c7…a3be
2 touches
0 conflicts
0xb504cd7e…5a81
0x0594c7…a3be
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: 0x188d586d…f9ea8e
1 conflict on slot 0x01e7b86585…4d6e6f
Audit this contract →
← previous block·next block →recent activity