← previous blocknext block →recent activity

Analyzing

Block #92,371,347

17 transactions · 16 stateful · 2026-08-02 02:38:32 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,371,347  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc44becc2…6043

0x34b655…2a6f

6 touches
3 conflicts

0x7a2fc410…c088

0x34b655…2a6f

6 touches
3 conflicts

0x2a53b0a1…a22d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x33877d7a…b21a

0x34b655…2a6f

4 touches
1 conflict

0x3cd98e7d…4628

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity