← previous blocknext block →recent activity
Analyzing
Block #77,341,105
35 transactions · 22 stateful · 2026-05-27 12:23:52 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,341,105 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w010w112w013w114w215w317w018w119w222w324w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x4eeec90d…8313
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0001
0x659bd0…a9da
4 touches
1 conflict
0x08d53462…97ef
0x69df8a…6292
4 touches
1 conflict
0x5a409e7f…09b6
0x69df8a…6292
4 touches
1 conflict
0x7a12283f…b18a
0x69df8a…6292
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity