← previous blocknext block →recent activity

Analyzing

Block #84,318,491

26 transactions · 22 stateful · 2026-06-28 20:15:35 UTC

Parallelism

73/100

Blocked

41%

Avg conflicts / tx

0.54

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,318,491  ·  26 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

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x1ca68aab…5e4a

0x34b655…2a6f

6 touches
3 conflicts

0xc05b880b…7746

0xa6afd3…d132

4 touches
1 conflict

0x0ad4dbe8…ae93

0x34b655…2a6f

4 touches
1 conflict

0x9aac8cba…35f4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd2cdfa3f…f071

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

← previous block·next block →recent activity