← previous blocknext block →recent activity

Analyzing

Block #74,649,153

15 transactions · 13 stateful · 2026-05-15 01:04:54 UTC

Parallelism

73/100

Blocked

46%

Avg conflicts / tx

0.87

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,649,153  ·  15 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x96112d2d…8214

0x065c9d…c394

5 touches
3 conflicts

0x07de1a81…2f5e

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xba279bbc…8dd6

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity