← previous blocknext block →recent activity

Analyzing

Block #94,901,700

20 transactions · 20 stateful · 2026-08-10 23:04:34 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,901,700  ·  20 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

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x2021fb2a…d63c

0x34b655…2a6f

4 touches
1 conflict

0x2592d715…a50e

0x34b655…2a6f

4 touches
1 conflict

0x27754bd4…96ae

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x3c955e7e…ef5e

0x34b655…2a6f

4 touches
1 conflict

0x6135a6eb…c6bb

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

6 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity