← previous blocknext block →recent activity
Analyzing
Block #75,078,910
17 transactions · 16 stateful · 2026-05-17 00:54:55 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,078,910 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w110w011w112w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
8 touches
6 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x1f4c677f…7308
0x34b655…2a6f
4 touches
1 conflict
0x578e7f66…1b56
0x34b655…2a6f
4 touches
1 conflict
0x5e24c5e6…330d
0x754704…b603
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x7b97d40a…09ed
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: 0xe7cd86e1…0fc82d
6 conflicts on slot 0xc4e19ae47e…dc0788
Audit this contract →
← previous block·next block →recent activity