← previous blocknext block →recent activity
Analyzing
Block #77,341,166
36 transactions · 23 stateful · 2026-05-27 12:24:17 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #77,341,166 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w18w19w010w112w016w122w228w029w130w231w332w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdf8c628d…34f2
0xa6afd3…d132
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xeeb38aa7…8f00
0x34b655…2a6f
6 touches
3 conflicts
0x8876d94c…8435
0x2a68ba…90c5
6 touches
3 conflicts
0xe8aab7db…a319
0xa6afd3…d132
6 touches
3 conflicts
0xe4b08559…6a03
0xa6afd3…d132
5 touches
3 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: Perpl
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity