← previous blocknext block →recent activity
Analyzing
Block #84,357,807
41 transactions · 26 stateful · 2026-06-29 00:37:41 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,357,807 · 41 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
1w02w13w25w06w39w010w121w122w024w025w026w127w128w433w034w136w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0xe8a155a6…cf24
0x34b655…2a6f
6 touches
3 conflicts
0x5fd0e7ac…8495
0xd32edf…ff58
5 touches
3 conflicts
0x1b159f3d…9163
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity