← previous blocknext block →recent activity
Analyzing
Block #84,509,766
33 transactions · 28 stateful · 2026-06-29 17:30:51 UTC
Parallelism
85/100
Blocked
54%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,509,766 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w110w011w114w015w116w217w318w421w222w225w327w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x89ef0dba…31e2
0x34b655…2a6f
6 touches
3 conflicts
0xa3010808…6585
0x34b655…2a6f
6 touches
3 conflicts
0xa6f7ec90…7bc9
0x34b655…2a6f
6 touches
3 conflicts
0xbb96f8af…205f
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity