← previous blocknext block →recent activity
Analyzing
Block #77,219,655
14 transactions · 12 stateful · 2026-05-26 22:53:15 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,219,655 · 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
1w05w16w09w112w013w1
- 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
0xeea99bee…e77f
0x6f4756…dd5b
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x08ba5be0…89d9
0xc39161…2de7
4 touches
1 conflict
0x2ea01b4c…c231
0xc39161…2de7
4 touches
1 conflict
0x71e5f48f…d281
0xc39161…2de7
4 touches
1 conflict
0xbd25225a…c493
0xc39161…2de7
4 touches
1 conflict
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