← previous blocknext block →recent activity

Analyzing

Block #92,459,437

19 transactions · 19 stateful · 2026-08-02 10:01:31 UTC

Parallelism

63/100

Blocked

58%

Avg conflicts / tx

1.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,459,437  ·  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

0x00000000…000a

0x90c374…be45

14 touches
21 conflicts

0x00000000…000b

0x90c374…be45

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xa4e9800f…4ab1

0x34b655…2a6f

6 touches
3 conflicts

0xf60d8303…14a0

0x34b655…2a6f

4 touches
1 conflict

0xa6311649…0132

0x34b655…2a6f

4 touches
1 conflict

0xcbc4e5fb…95b0

0x336ed4…c59c

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: 0x90c3747c…0ebe45

21 conflicts on slot 0x0000000000…00000a

← previous block·next block →recent activity