← previous blocknext block →recent activity

Analyzing

Block #74,255,150

16 transactions · 15 stateful · 2026-05-13 05:15:03 UTC

Parallelism

50/100

Blocked

53%

Avg conflicts / tx

1.81

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,255,150  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x99574012…cbeb

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xa333eeb1…8d97

0x065c9d…c394

2 touches
0 conflicts

0xad632dfc…f9be

0x065c9d…c394

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity