← previous blocknext block →recent activity

Analyzing

Block #92,974,700

20 transactions · 18 stateful · 2026-08-04 05:14:45 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,974,700  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x521e7b60…777f

0x34b655…2a6f

8 touches
6 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0x28ceceef…ecc2

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity