← previous blocknext block →recent activity

Analyzing

Block #74,188,297

17 transactions · 16 stateful · 2026-05-12 21:50:29 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

2.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,188,297  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x2d153e58…4eac

0x58e158…3d57

2 touches
0 conflicts

0x3dea5c3d…5fb8

0x58e158…3d57

2 touches
0 conflicts

0x76a96399…9bbf

0x58e158…3d57

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity