← previous blocknext block →recent activity
Analyzing
Block #73,037,233
23 transactions · 19 stateful · 2026-05-07 13:52:20 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,037,233 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w29w010w111w212w313w414w515w617w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x3702b140…97ea
0x34b655…2a6f
8 touches
6 conflicts
0xdaca243a…f9de
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x005fb969…2d97
0x34b655…2a6f
6 touches
3 conflicts
0xd25a8ec5…2fd1
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 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: Perpl
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity