← previous blocknext block →recent activity

Analyzing

Block #92,525,703

15 transactions · 15 stateful · 2026-08-02 15:34:50 UTC

Parallelism

47/100

Blocked

60%

Avg conflicts / tx

0.8

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,525,703  ·  15 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x74c3e5e7…55ee

0x34b655…2a6f

4 touches
1 conflict

0x7e1faa73…bfbf

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xa0d3a786…91d9

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity