← previous blocknext block →recent activity

Analyzing

Block #74,505,344

31 transactions · 22 stateful · 2026-05-14 09:00:05 UTC

Parallelism

81/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,505,344  ·  31 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0de7749d…5bef

0x34b655…2a6f

6 touches
3 conflicts

0x5d32a251…d929

0x34b655…2a6f

6 touches
3 conflicts

0x44ad89ba…cf83

0x23c26b…7777

4 touches
1 conflict

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity