pev.One block, wave by wave
analyticsdocs
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,455,799
17 transactions · 11 stateful · 2026-05-14 03:30:08 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,455,799 · 17 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
2w04w05w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0178c2de…b37d
0x8d66a4…3095
4 touches
1 conflict
0x74825c4e…32e9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a4
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a5
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
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
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity
Feature requests