← previous blocknext block →recent activity

Analyzing

Block #74,956,914

14 transactions · 12 stateful · 2026-05-16 11:19:52 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,956,914  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xf8f6d22b…3617

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x14c8f1af…c4a6

0x065c9d…c394

2 touches
0 conflicts

0x2c57624a…89aa

0x065c9d…c394

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity