← previous blocknext block →recent activity
Analyzing
Block #84,511,970
28 transactions · 21 stateful · 2026-06-29 17:45:34 UTC
Parallelism
86/100
Blocked
57%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,511,970 · 28 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
1w02w13w24w35w26w07w114w015w116w217w319w020w021w222w323w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x9b5be693…cf27
0xd32edf…ff58
7 touches
6 conflicts
0x0f8965bb…e238
0x34b655…2a6f
6 touches
3 conflicts
0x6e2becf4…0c5f
0x34b655…2a6f
6 touches
3 conflicts
0x8766b1c5…62db
0x34b655…2a6f
6 touches
3 conflicts
0x89ef0dba…31e2
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
0x34b655…2a6f
6 touches
3 conflicts
0xacbc3fbb…fe8e
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity