← previous blocknext block →recent activity

Analyzing

Block #82,974,977

22 transactions · 19 stateful · 2026-06-22 14:49:59 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,974,977  ·  22 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

0xea9e7e38…819b

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc8c54a2d…0f66

0x34b655…2a6f

4 touches
2 conflicts

0x2eb3373a…8aff

0x34b655…2a6f

4 touches
1 conflict

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x74f95963…01a2

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 0xea9e7e3891…a0819b

← previous block·next block →recent activity