← previous blocknext block →recent activity
Analyzing
Block #77,352,300
35 transactions · 22 stateful · 2026-05-27 13:38:19 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #77,352,300 · 35 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
1w03w17w08w19w210w311w412w016w129w030w131w232w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x4b8f35e2…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
4 touches
1 conflict
0x10abefc9…c9bc
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: Perpl
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity