← previous blocknext block →recent activity
Analyzing
Block #75,622,069
27 transactions · 15 stateful · 2026-05-19 13:31:26 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,622,069 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w111w012w113w214w322w023w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb818fd2b…b609
0xd32edf…ff58
7 touches
6 conflicts
0x1630ed91…9774
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x5a8b47f0…7fbd
0x34b655…2a6f
4 touches
1 conflict
0x6259b44a…0a9b
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