← previous blocknext block →recent activity

Analyzing

Block #74,248,490

16 transactions · 15 stateful · 2026-05-13 04:30:49 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,248,490  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x911772c2…03ae

0x065c9d…c394

4 touches
1 conflict

0xa51ca39b…7b7b

0x065c9d…c394

4 touches
1 conflict

0x3d6a14e0…8cc4

0x065c9d…c394

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity