← previous blocknext block →recent activity
Analyzing
Block #75,479,684
14 transactions · 11 stateful · 2026-05-18 21:33:08 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,479,684 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x6a7b9d99…bb3e
0x065c9d…c394
3 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x98f36ffe…b25c
0x065c9d…c394
2 touches
0 conflicts
0xe3246320…3cb5
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0xb245fe3647…73d765
Audit this contract →
← previous block·next block →recent activity