← previous blocknext block →recent activity
Analyzing
Block #77,185,278
15 transactions · 11 stateful · 2026-05-26 19:02:23 UTC
Parallelism
87/100
Blocked
27%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,185,278 · 15 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
1w02w13w04w19w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x437e6c1f…2cb3
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xb2a856e8…d747
0x9f3832…4ae4
4 touches
1 conflict
0xb2a856e8…d748
0x9f3832…4ae4
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xb6c3d394…acd2
0xe1c8b7…3022
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: 0x9f383273…514ae4
1 conflict on slot 0x437e6c1f96…2f2cb3
Audit this contract →
← previous block·next block →recent activity