← previous blocknext block →recent activity
Analyzing
Block #75,139,809
8 transactions · 7 stateful · 2026-05-17 07:41:19 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,139,809 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8538a5f8…7f37
0x065c9d…c394
2 touches
0 conflicts
0x9d111572…58aa
0x065c9d…c394
2 touches
0 conflicts
0xa6ea4218…2233
0x065c9d…c394
2 touches
0 conflicts
0xb7feed21…cdd6
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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 0xef17b8cd5c…709511
Audit this contract →
← previous block·next block →recent activity