← previous blocknext block →recent activity

Analyzing

Block #74,190,684

24 transactions · 22 stateful · 2026-05-12 22:06:22 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,190,684  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x41335ddf…94b9

0x34b655…2a6f

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x3817764d…242b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd2bcf2a3…9360

0x34b655…2a6f

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe9bb0bed…5a14

0xd32edf…ff58

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

6 conflicts on slot 0x41335ddf94…5594b9

← previous block·next block →recent activity