← previous blocknext block →recent activity
Analyzing
Block #77,362,539
23 transactions · 21 stateful · 2026-05-27 14:46:37 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,362,539 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w39w410w012w118w019w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xe2884e77…af55
0xd32edf…ff58
7 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0xf0d3c3f0…c09e
0xa6afd3…d132
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…003d
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity