← previous blocknext block →recent activity
Analyzing
Block #84,258,076
24 transactions · 22 stateful · 2026-06-28 13:33:04 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,258,076 · 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
1w02w13w04w05w16w27w38w09w110w011w112w214w015w216w117w222w023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xe1e58d05…117f
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb353efd4…bee7
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity