← previous blocknext block →recent activity

Analyzing

Block #93,355,624

19 transactions · 19 stateful · 2026-08-05 13:11:44 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,355,624  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xac3e4969…39e9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

6 touches
3 conflicts

0xc1d936ef…b7ac

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

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 0xca841faae5…71486a

← previous block·next block →recent activity