← previous blocknext block →recent activity
Analyzing
Block #84,497,296
11 transactions · 10 stateful · 2026-06-29 16:07:38 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,497,296 · 11 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
2w04w18w09w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6836671…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc3c7cf34…43da
0x34b655…2a6f
4 touches
1 conflict
0x03c8cd85…798a
0x34b655…2a6f
2 touches
0 conflicts
0x0f44b5ba…e7bf
0x34b655…2a6f
2 touches
0 conflicts
0x62aed667…7bd6
0x34b655…2a6f
2 touches
0 conflicts
0x6a210947…e2a1
0x34b655…2a6f
2 touches
0 conflicts
0x76bb28fc…2ce7
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: Perpl
3 conflicts on slot 0xb683667184…055c3c
Audit this contract →
← previous block·next block →recent activity