← previous blocknext block →recent activity
Analyzing
Block #75,741,982
24 transactions · 23 stateful · 2026-05-20 02:50:15 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #75,741,982 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w510w611w712w815w117w220w121w222w323w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x0711ec2d…d973
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x99f080dc…58c1
0x34b655…2a6f
16 touches
28 conflicts
0xd49762c9…1359
0x34b655…2a6f
16 touches
28 conflicts
0x908d4442…2c4b
0x34b655…2a6f
16 touches
28 conflicts
0x9948dde8…6a26
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity