← previous blocknext block →recent activity

Analyzing

Block #74,287,316

12 transactions · 10 stateful · 2026-05-13 08:48:52 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,287,316  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…0004

0xd5b70d…615b

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x52e0d3b4…b8ff

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 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: 0xd5b70d70…f4615b

3 conflicts on slot 0x0000000000…000004

← previous block·next block →recent activity