← previous blocknext block →recent activity
Analyzing
Block #84,348,949
24 transactions · 22 stateful · 2026-06-28 23:38:34 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,348,949 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w09w110w211w314w015w117w018w119w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x7b7af531…48f1
0xa6afd3…d132
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x0881ff59…2164
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity