← previous blocknext block →recent activity

Analyzing

Block #92,454,853

19 transactions · 19 stateful · 2026-08-02 09:38:28 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.37

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,454,853  ·  19 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

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0xa558e115…fc88

0x34b655…2a6f

6 touches
3 conflicts

0x51c64da3…3b8c

0x34b655…2a6f

5 touches
3 conflicts

0x783c9e6e…c949

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

15 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity