← previous blocknext block →recent activity
Analyzing
Block #84,082,310
25 transactions · 21 stateful · 2026-06-27 18:02:24 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,082,310 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w212w013w315w117w118w219w422w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfdd8cf3f…4bd9
0x065c9d…c394
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity