← previous blocknext block →recent activity
Analyzing
Block #84,288,753
21 transactions · 11 stateful · 2026-06-28 16:57:29 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,288,753 · 21 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
1w02w13w24w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x20e57a61…028c
0x34b655…2a6f
2 touches
0 conflicts
0x23eaa37b…6efc
0x34b655…2a6f
2 touches
0 conflicts
0x4c9c15e6…7702
0x34b655…2a6f
2 touches
0 conflicts
0x4ec368ea…7181
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity