← previous blocknext block →recent activity
Analyzing
Block #75,530,315
22 transactions · 16 stateful · 2026-05-19 03:19:04 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,530,315 · 22 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
1w02w03w14w28w010w119w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x08dd3d…a583
6 touches
3 conflicts
0xff9eec93…1598
0x08dd3d…a583
6 touches
3 conflicts
0x2b936aa5…05e2
0x141b1d…9583
6 touches
3 conflicts
0x2b936aa5…05e3
0x141b1d…9583
6 touches
3 conflicts
0x2b936aa5…05e5
0x141b1d…9583
6 touches
3 conflicts
0x00000000…0003
0x2ae0cf…3d4e
6 touches
3 conflicts
0xdaaa2a2c…6609
0x754704…b603
6 touches
3 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
6 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity