← previous blocknext block →recent activity
Analyzing
Block #84,335,720
18 transactions · 13 stateful · 2026-06-28 22:10:24 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,335,720 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
4 touches
1 conflict
0x18b11fba…c92a
0x34b655…2a6f
4 touches
1 conflict
0x1b1df992…40eb
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x2cc8c2a5…eb26
0x34b655…2a6f
4 touches
1 conflict
0x31650404…ef0e
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