← previous blocknext block →recent activity

Analyzing

Block #74,336,430

17 transactions · 16 stateful · 2026-05-13 14:15:38 UTC

Parallelism

41/100

Blocked

63%

Avg conflicts / tx

2.71

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,336,430  ·  17 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa472d565…9fe4

0x3bd359…433a

20 touches
45 conflicts

0x70d375f4…7a02

0xa7283d…0ace

16 touches
28 conflicts

0x70d375f4…7a01

0xa7283d…0ace

16 touches
28 conflicts

0x8fa7a69c…8fd7

0x2e8df2…7777

16 touches
28 conflicts

0x70d375f4…7a00

0xa7283d…0ace

16 touches
28 conflicts

0x70d375f4…79ff

0xa7283d…0ace

16 touches
28 conflicts

0x00000000…0002

0xa7283d…0ace

16 touches
28 conflicts

0x536e2740…61ac

0x3bd359…433a

16 touches
28 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: 0x3bd359c1…15433a

45 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity