← previous blocknext block →recent activity
Analyzing
Block #77,783,942
26 transactions · 22 stateful · 2026-05-29 13:35:37 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #77,783,942 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w18w09w110w212w313w414w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x9885a25f…292c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x2d17762e…10e0
0xd32edf…ff58
3 touches
1 conflict
0x49cbdb1b…bda4
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: 0xab35264b…1cfa38
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity