← previous blocknext block →recent activity

Analyzing

Block #93,361,289

26 transactions · 23 stateful · 2026-08-05 13:40:13 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,361,289  ·  26 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

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x91e8d927…3a11

0x34b655…2a6f

6 touches
3 conflicts

0x3d158563…8713

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4a4

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x842dd93b…a41f

0x34b655…2a6f

4 touches
1 conflict

0x8765edd1…a7d5

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 0x45ea7a9723…bdbbb3

← previous block·next block →recent activity