← previous blocknext block →recent activity

Analyzing

Block #93,254,098

11 transactions · 11 stateful · 2026-08-05 04:41:16 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,254,098  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x79fd259b…19b2

0x34b655…2a6f

4 touches
1 conflict

0x9210e826…1414

0x34b655…2a6f

4 touches
1 conflict

0xc84296b4…7dee

0x34b655…2a6f

4 touches
1 conflict

0xf51ec09c…b4a9

0x34b655…2a6f

4 touches
1 conflict

0xfcc8f826…7c5f

0x34b655…2a6f

4 touches
1 conflict

0xfe768012…b65e

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0110331c…b891

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

1 conflict on slot 0x79fd259b46…6419b2

← previous block·next block →recent activity