← previous blocknext block →recent activity
Analyzing
Block #73,924,371
18 transactions · 18 stateful · 2026-05-11 16:32:02 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,924,371 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w39w011w112w213w316w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee230b20…5a0f
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
8 touches
6 conflicts
0xac8e97a0…8426
0x34b655…2a6f
8 touches
6 conflicts
0x9be2b99a…a959
0x34b655…2a6f
8 touches
6 conflicts
0x96844849…b4b0
0x34b655…2a6f
8 touches
6 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
8 touches
6 conflicts
0x4f483049…3cc7
0x34b655…2a6f
8 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
10 conflicts on slot 0xee230b202a…c05a0f
Audit this contract →
← previous block·next block →recent activity