← previous blocknext block →recent activity
Analyzing
Block #84,063,948
32 transactions · 22 stateful · 2026-06-27 16:00:09 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,063,948 · 32 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
3w06w18w010w114w015w116w217w018w319w420w122w025w226w227w331w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x763dd151…d9de
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x117f1699…b264
0xa6afd3…d132
6 touches
3 conflicts
0x8726ff39…3be8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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