← previous blocknext block →recent activity

Analyzing

Block #93,346,494

19 transactions · 18 stateful · 2026-08-05 12:25:49 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,346,494  ·  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

0x87fcd5db…d2e6

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2d651956…12e8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x808129fc…f97d

0x34b655…2a6f

6 touches
3 conflicts

0xa279b18d…63bc

0x34b655…2a6f

6 touches
3 conflicts

0xa6389d47…9a28

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

6 conflicts on slot 0x87fcd5db2b…26d2e6

← previous block·next block →recent activity