← previous blocknext block →recent activity
Analyzing
Block #77,504,510
13 transactions · 8 stateful · 2026-05-28 06:32:14 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,504,510 · 13 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x10abefc9…c9bc
0x69df8a…6292
2 touches
0 conflicts
0x10d80fee…dbda
0x69df8a…6292
2 touches
0 conflicts
0x5a409e7f…09b6
0x69df8a…6292
2 touches
0 conflicts
0x66d63204…51a0
0x69df8a…6292
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 0xf9b8ae99dc…3532b3
Audit this contract →
← previous block·next block →recent activity