← previous blocknext block →recent activity

Analyzing

Block #94,915,032

23 transactions · 19 stateful · 2026-08-11 00:11:37 UTC

Parallelism

91/100

Blocked

26%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,915,032  ·  23 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

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0x11b69a7e…334e

0x01bff4…1071

4 touches
1 conflict

0xb39cb1d8…effa

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…0002

0xeae24c…0be0

4 touches
1 conflict

0x35b89cd8…5092

0x34b655…2a6f

2 touches
0 conflicts

0x578f440f…33e0

0x34b655…2a6f

2 touches
0 conflicts

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 0xb3fb9fb561…7664db

← previous block·next block →recent activity