← previous blocknext block →recent activity

Analyzing

Block #93,362,907

18 transactions · 17 stateful · 2026-08-05 13:48:21 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,362,907  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x45ea7a97…bbb3

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0d876411…c303

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x107b89e4…470d

0x34b655…2a6f

4 touches
1 conflict

0x1a646e42…3c44

0x34b655…2a6f

4 touches
1 conflict

0x3ed31132…62b6

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

10 conflicts on slot 0x45ea7a9723…bdbbb3

← previous block·next block →recent activity