← previous blocknext block →recent activity

Analyzing

Block #74,040,933

12 transactions · 9 stateful · 2026-05-12 05:30:01 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,040,933  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x266fb969…8be1

0x065c9d…c394

2 touches
0 conflicts

0x78223073…9268

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000b

0x097d40…9920

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity