← previous blocknext block →recent activity

Analyzing

Block #83,623,890

24 transactions · 21 stateful · 2026-06-25 15:05:32 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,623,890  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0x5aed1bd2…7afa

0x34b655…2a6f

6 touches
3 conflicts

0x5fad6fee…7714

0x34b655…2a6f

6 touches
3 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

6 touches
3 conflicts

0x967b4a40…7a78

0x34b655…2a6f

6 touches
3 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity