← previous blocknext block →recent activity
Analyzing
Block #76,239,173
14 transactions · 13 stateful · 2026-05-22 10:03:27 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,239,173 · 14 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
1w02w14w05w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x68728b15…33fc
0x34b655…2a6f
4 touches
1 conflict
0xb96e29a5…0419
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0xbd6e260c…3720
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
3 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity