← previous blocknext block →recent activity

Analyzing

Block #92,528,625

23 transactions · 20 stateful · 2026-08-02 15:49:32 UTC

Parallelism

78/100

Blocked

40%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,528,625  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xff196840…a453

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x19e1da6e…4a72

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0xe4636320…f407

0x34b655…2a6f

4 touches
1 conflict

0x55b2239f…fec5

0x34b655…2a6f

4 touches
1 conflict

0x6c26d635…1bbf

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 0xff19684070…f2a453

← previous block·next block →recent activity