← previous blocknext block →recent activity

Analyzing

Block #93,347,349

25 transactions · 25 stateful · 2026-08-05 12:30:07 UTC

Parallelism

56/100

Blocked

52%

Avg conflicts / tx

1.52

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #93,347,349  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

8 touches
6 conflicts

0x424934c8…f2f1

0x34b655…2a6f

8 touches
6 conflicts

0x94bb14fe…8f47

0x34b655…2a6f

6 touches
3 conflicts

0xa6389d47…9a28

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x808129fc…f97d

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity