← previous blocknext block →recent activity
Analyzing
Block #84,335,578
32 transactions · 22 stateful · 2026-06-28 22:09:27 UTC
Parallelism
88/100
Blocked
59%
Avg conflicts / tx
0.66
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,335,578 · 32 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
2w05w16w08w09w110w217w018w119w220w321w022w123w124w225w328w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xec85756f…0ba2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x0833f1ab…71e7
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity