← previous blocknext block →recent activity
Analyzing
Block #84,336,079
24 transactions · 20 stateful · 2026-06-28 22:12:48 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,336,079 · 24 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
2w03w14w25w38w09w112w013w114w215w316w018w419w120w522w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
4 touches
1 conflict
0x0c807316…48f8
0x34b655…2a6f
4 touches
1 conflict
0x3dcad451…7938
0x34b655…2a6f
4 touches
1 conflict
0x668bb814…8106
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity