← previous blocknext block →recent activity
Analyzing
Block #77,516,853
14 transactions · 9 stateful · 2026-05-28 07:54:30 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,516,853 · 14 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
4w05w010w1
- 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
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
2 touches
0 conflicts
0x8b36b652…650a
0x34b655…2a6f
2 touches
0 conflicts
0x43047d41…5cd4
0x69df8a…6292
2 touches
0 conflicts
0x5a409e7f…09b6
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