← previous blocknext block →recent activity
Analyzing
Block #84,259,309
17 transactions · 17 stateful · 2026-06-28 13:41:14 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,259,309 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w07w19w011w212w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99910689…8959
0x34b655…2a6f
6 touches
3 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xc0f29314…17f7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
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 0x99910689d7…f88959
Audit this contract →
← previous block·next block →recent activity