← previous blocknext block →recent activity

Analyzing

Block #84,130,685

15 transactions · 11 stateful · 2026-06-27 23:24:47 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #84,130,685  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x39f7e392…23ee

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7cb2f3fa…4836

0x34b655…2a6f

4 touches
1 conflict

0x99c320a0…b4a8

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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

1 conflict on slot 0x39f7e3924c…cc23ee

← previous block·next block →recent activity