← previous blocknext block →recent activity

Analyzing

Block #91,416,637

24 transactions · 21 stateful · 2026-07-29 18:35:20 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,416,637  ·  24 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

0x00000000…0002

0x48cba2…b48b

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xb4e0a934…5fc7

0x34b655…2a6f

4 touches
1 conflict

0x5a4d5f09…5094

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xb05cd4f5…73d0

0x2b46c0…1669

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: 0x48cba278…e2b48b

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity