← previous blocknext block →recent activity
Analyzing
Block #75,198,645
8 transactions · 6 stateful · 2026-05-17 14:14:21 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,198,645 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x749437cf…2fc0
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc1
0x2880ab…7b43
2 touches
0 conflicts
0x070a562a…8147
0x34b655…2a6f
2 touches
0 conflicts
0x37cfaf01…4a46
0x34b655…2a6f
2 touches
0 conflicts
0x578e7f66…1b56
0x34b655…2a6f
2 touches
0 conflicts
0x6d0c65d9…c36f
0x34b655…2a6f
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 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity