← previous blocknext block →recent activity

Analyzing

Block #91,779,515

18 transactions · 15 stateful · 2026-07-31 01:01:44 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,779,515  ·  18 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5fab7fbe…1ce5

0x34b655…2a6f

4 touches
1 conflict

0x739a54da…8647

0x34b655…2a6f

4 touches
1 conflict

0x784eaad2…d176

0x34b655…2a6f

4 touches
1 conflict

0x805ef821…67d4

0x34b655…2a6f

4 touches
1 conflict

0x898d9b8a…d1ef

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity