← previous blocknext block →recent activity
Analyzing
Block #73,918,364
20 transactions · 18 stateful · 2026-05-11 15:52:04 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,918,364 · 20 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
1w02w13w24w06w19w010w111w212w313w416w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
16 touches
28 conflicts
0xe1a70e73…1293
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
8 touches
6 conflicts
0x4f483049…3cc7
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 conflicts
0xa6cee2b4…9cec
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
28 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity