← previous blocknext block →recent activity
Analyzing
Block #75,098,711
10 transactions · 6 stateful · 2026-05-17 03:07:09 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,098,711 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x4eb1f171…b075
0x065c9d…c394
2 touches
0 conflicts
0x7332ee6e…5125
0x065c9d…c394
2 touches
0 conflicts
0xa376ba38…a1f8
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
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 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity