← previous blocknext block →recent activity

Analyzing

Block #84,497,549

18 transactions · 17 stateful · 2026-06-29 16:09:20 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,497,549  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x9ad4d28a…c788

0x34b655…2a6f

6 touches
3 conflicts

0x2d6f8c47…8e93

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xab86573c…682e

0x34b655…2a6f

4 touches
1 conflict

0xb6836671…5c3c

0x34b655…2a6f

4 touches
1 conflict

0xbc9aaf19…8cfd

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

3 conflicts on slot 0x9ad4d28af1…c2c788

← previous block·next block →recent activity