← previous blocknext block →recent activity

Analyzing

Block #74,423,301

20 transactions · 18 stateful · 2026-05-13 23:53:44 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,423,301  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb95b0d51…0da3

0x34b655…2a6f

8 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x496b4372…d222

0x065c9d…c394

7 touches
6 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x7997f8…b3c9

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0x34b6552d…112a6f

6 conflicts on slot 0xb95b0d51d2…380da3

← previous block·next block →recent activity