← previous blocknext block →recent activity

Analyzing

Block #84,291,061

19 transactions · 16 stateful · 2026-06-28 17:12:53 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,291,061  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x23ab8481…52d5

0x34b655…2a6f

4 touches
1 conflict

0x32229dd3…4dbb

0x34b655…2a6f

4 touches
1 conflict

0x37d710c8…45c1

0x34b655…2a6f

4 touches
1 conflict

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x64db8826…ac87

0x34b655…2a6f

4 touches
1 conflict

0x71211f46…bbfd

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 0x482471adbb…39122f

← previous block·next block →recent activity