← previous blocknext block →recent activity
Analyzing
Block #77,340,712
28 transactions · 22 stateful · 2026-05-27 12:21:15 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,340,712 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w19w211w114w015w116w118w221w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x9fc6a7d3…2f62
0xd32edf…ff58
5 touches
3 conflicts
0x05eea3e3…5846
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8e7cafc0…4c76
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity