← previous blocknext block →recent activity

Analyzing

Block #91,983,231

17 transactions · 16 stateful · 2026-07-31 18:06:35 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,983,231  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x991e2e20…94a6

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc7981744…932f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x427d1120…4eb1

0x34b655…2a6f

4 touches
1 conflict

0x09b6d501…a338

0x34b655…2a6f

4 touches
1 conflict

0x4abaedb1…65b9

0x34b655…2a6f

4 touches
1 conflict

0x5878b60b…ea9c

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x991e2e2071…6194a6

← previous block·next block →recent activity