← previous blocknext block →recent activity
Analyzing
Block #84,311,697
20 transactions · 20 stateful · 2026-06-28 19:30:22 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,311,697 · 20 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
1w02w13w26w07w18w212w314w115w216w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f3fc680…f989
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x23ab8481…52d5
0x34b655…2a6f
4 touches
1 conflict
0x59f0e3be…4a21
0x34b655…2a6f
4 touches
1 conflict
0x77674e3c…0f43
0x34b655…2a6f
4 touches
1 conflict
0x8a01f41e…d4bf
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 0x5f3fc68024…49f989
Audit this contract →
← previous block·next block →recent activity