← previous blocknext block →recent activity

Analyzing

Block #93,231,892

19 transactions · 16 stateful · 2026-08-05 02:49:37 UTC

Parallelism

58/100

Blocked

63%

Avg conflicts / tx

1.63

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,231,892  ·  19 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

0x4acbdbcf…a8c6

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0x3550075a…fb0f

0x34b655…2a6f

6 touches
3 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity