← previous blocknext block →recent activity
Analyzing
Block #84,499,083
19 transactions · 17 stateful · 2026-06-29 16:19:34 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,499,083 · 19 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
1w02w04w16w07w18w09w010w111w212w315w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x04f26bce…2a8e
0x34b655…2a6f
6 touches
3 conflicts
0x00e21a9f…3583
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2328941c…84d3
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