← previous blocknext block →recent activity

Analyzing

Block #83,631,490

37 transactions · 30 stateful · 2026-06-25 15:56:18 UTC

Parallelism

68/100

Blocked

77%

Avg conflicts / tx

1.7

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #83,631,490  ·  37 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x0261169c…8834

0xd32edf…ff58

9 touches
10 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xda7f9bd2…e332

0x34b655…2a6f

8 touches
6 conflicts

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity