← previous blocknext block →recent activity
Analyzing
Block #75,269,869
25 transactions · 21 stateful · 2026-05-17 22:10:22 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,269,869 · 25 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
2w03w14w06w07w08w19w211w312w415w116w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xe6455d1f…1029
0x754704…b603
10 touches
10 conflicts
0x0d0b2509…074d
0x3bd359…433a
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x0711ec2d…d973
0x34b655…2a6f
8 touches
6 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 conflicts
0x99f080dc…58c1
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity