← previous blocknext block →recent activity
Analyzing
Block #77,782,780
21 transactions · 19 stateful · 2026-05-29 13:27:56 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #77,782,780 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w26w37w48w09w110w211w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x301a6cf4…8cfb
0x065c9d…c394
6 touches
3 conflicts
0x0d906816…94fc
0x065c9d…c394
5 touches
3 conflicts
0xdb9ac7a7…e621
0x065c9d…c394
4 touches
1 conflict
0xf867fd0c…51d2
0x065c9d…c394
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: 0xab35264b…1cfa38
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity