← previous blocknext block →recent activity
Analyzing
Block #77,236,387
17 transactions · 12 stateful · 2026-05-27 00:45:49 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,236,387 · 17 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
2w06w17w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9948dde8…6a26
0x34b655…2a6f
4 touches
1 conflict
0xaa0d0542…d8ec
0x34b655…2a6f
4 touches
1 conflict
0xff5c097d…680c
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
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
3 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity