← previous blocknext block →recent activity

Analyzing

Block #92,540,678

21 transactions · 20 stateful · 2026-08-02 16:50:09 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,540,678  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x97684f09…980c

0x34b655…2a6f

6 touches
3 conflicts

0xad828968…49e4

0x34b655…2a6f

6 touches
3 conflicts

0x6e6b8ec7…2197

0x34b655…2a6f

6 touches
3 conflicts

0xd8ca0135…c1c3

0x34b655…2a6f

6 touches
3 conflicts

0x50260e8c…4789

0x34b655…2a6f

4 touches
1 conflict

0x64a785e4…0110

0x34b655…2a6f

4 touches
1 conflict

0x6c45a9f4…a2f0

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity