← previous blocknext block →recent activity

Analyzing

Block #74,216,161

15 transactions · 13 stateful · 2026-05-13 00:55:51 UTC

Parallelism

80/100

Blocked

23%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,216,161  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x5b5eb6a6…e3b0

0x065c9d…c394

2 touches
0 conflicts

0x6586e587…6e3f

0x065c9d…c394

2 touches
0 conflicts

0x6e8492c0…127f

0x065c9d…c394

2 touches
0 conflicts

0xccd80b65…644d

0x065c9d…c394

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity