← previous blocknext block →recent activity

Analyzing

Block #92,447,240

20 transactions · 20 stateful · 2026-08-02 09:00:10 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,447,240  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x6e6b8ec7…2197

0x34b655…2a6f

6 touches
3 conflicts

0x745a7fd6…5fea

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity