← previous blocknext block →recent activity

Analyzing

Block #84,570,022

25 transactions · 19 stateful · 2026-06-30 00:13:08 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.84

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,570,022  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x26918bca…6c75

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x1d7140ec…9f87

0x34b655…2a6f

4 touches
1 conflict

0x31f71c9d…20bb

0x34b655…2a6f

4 touches
1 conflict

0x42bb0ac5…6b33

0x34b655…2a6f

4 touches
1 conflict

0x5a8b47f0…7fbd

0x34b655…2a6f

4 touches
1 conflict

0x70638c24…1553

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity