← previous blocknext block →recent activity

Analyzing

Block #80,167,056

20 transactions · 15 stateful · 2026-06-09 14:42:19 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,167,056  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7ef9f6fb…99c5

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x901d9f30…67a4

0x34b655…2a6f

6 touches
3 conflicts

0xe50fb70e…8e70

0x34b655…2a6f

4 touches
1 conflict

0x8210fa51…bc92

0x34b655…2a6f

4 touches
1 conflict

0x85eb1316…bb9e

0x34b655…2a6f

4 touches
1 conflict

0x985d6016…3a64

0x34b655…2a6f

4 touches
1 conflict

0xa0f5612a…9804

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 0x7ef9f6fbc9…0199c5

← previous block·next block →recent activity