← previous blocknext block →recent activity
Analyzing
Block #75,079,607
21 transactions · 16 stateful · 2026-05-17 00:59:36 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,079,607 · 21 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
5w06w17w216w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0x6cb83e26…fe4f
0x34b655…2a6f
4 touches
1 conflict
0x89f9fa42…7eb3
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x96aa7e47…f584
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity