← previous blocknext block →recent activity
Analyzing
Block #73,921,903
23 transactions · 20 stateful · 2026-05-11 16:15:36 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,921,903 · 23 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
2w03w14w05w06w08w19w210w311w112w113w214w317w119w422w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee230b20…5a0f
0x34b655…2a6f
12 touches
15 conflicts
0xef2a8932…1398
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x4f483049…3cc7
0x34b655…2a6f
8 touches
6 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
8 touches
6 conflicts
0xc3aacf13…6b3d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x53667875…9f4a
0xd32edf…ff58
7 touches
6 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
15 conflicts on slot 0xee230b202a…c05a0f
Audit this contract →
← previous block·next block →recent activity