← previous blocknext block →recent activity
Analyzing
Block #75,087,725
26 transactions · 18 stateful · 2026-05-17 01:53:55 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,087,725 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w19w113w014w118w219w224w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0xbf38832c…7ae3
0x34b655…2a6f
6 touches
3 conflicts
0xa11bd7ea…20b4
0x34b655…2a6f
6 touches
3 conflicts
0x11f25e19…8bb1
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
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 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity