← previous blocknext block →recent activity
Analyzing
Block #75,902,141
12 transactions · 8 stateful · 2026-05-20 20:38:21 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,902,141 · 12 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48e4e1cf…f91b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf2d6d6e1…3d64
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x3a51cc5b…c22e
0x34b655…2a6f
3 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xc9efec82…fd4f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity