← previous blocknext block →recent activity

Analyzing

Block #93,234,368

19 transactions · 17 stateful · 2026-08-05 03:02:04 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,234,368  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

6 touches
3 conflicts

0x3464bbc5…a323

0xa6afd3…d132

6 touches
3 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 conflicts

0x2d651956…12e8

0x34b655…2a6f

4 touches
1 conflict

0x314add6a…c880

0x34b655…2a6f

4 touches
1 conflict

0x3944526b…c457

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

3 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity