← previous blocknext block →recent activity
Analyzing
Block #75,345,580
13 transactions · 9 stateful · 2026-05-18 06:37:05 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,345,580 · 13 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
1w02w13w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xc248a876…0b85
0x2a68ba…90c5
2 touches
1 conflict
0x58328489…223a
0x754704…b603
2 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
2 touches
0 conflicts
0xd49762c9…1359
0x34b655…2a6f
2 touches
0 conflicts
0x055d3c5e…4621
0x754704…b603
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 0x83f3d32000…25fb59
Audit this contract →
← previous block·next block →recent activity