← previous blocknext block →recent activity

Analyzing

Block #91,996,300

12 transactions · 9 stateful · 2026-07-31 19:12:19 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,996,300  ·  12 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

0xf9874e36…beed

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcc282b3d…e139

0x34b655…2a6f

4 touches
1 conflict

0xd3d2b624…594f

0x34b655…2a6f

4 touches
1 conflict

0xe67c40ec…8793

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x63bed776…8d4a

0x34b655…2a6f

4 touches
1 conflict

0x63bed776…8d4b

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

1 conflict on slot 0xf9874e3690…90beed

← previous block·next block →recent activity