← previous blocknext block →recent activity
Analyzing
Block #73,210,052
24 transactions · 19 stateful · 2026-05-08 09:02:15 UTC
Parallelism
88/100
Blocked
47%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,210,052 · 24 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
1w02w13w04w15w07w18w210w211w114w018w222w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4730a2d…3538
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x3f8c63c9…3594
0xd32edf…ff58
5 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xfddaf4ac…ec62
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
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: Perpl
3 conflicts on slot 0xf4730a2de3…ef3538
Audit this contract →
← previous block·next block →recent activity