← previous blocknext block →recent activity
Analyzing
Block #75,198,823
26 transactions · 19 stateful · 2026-05-17 14:15:31 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,198,823 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w08w110w113w217w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x61f03f99…5ae5
0xd32edf…ff58
5 touches
3 conflicts
0x1dd35dcc…641b
0x34b655…2a6f
4 touches
1 conflict
0x2905340c…dbc6
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x3bb07d5e…582e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity