← previous blocknext block →recent activity

Analyzing

Block #74,344,943

31 transactions · 26 stateful · 2026-05-13 15:12:15 UTC

Parallelism

65/100

Blocked

69%

Avg conflicts / tx

2.1

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,344,943  ·  31 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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…0002

0xab3526…fa38

22 touches
55 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x17a7f697…dcb2

0x1b6862…e19c

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: 0xab35264b…1cfa38

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity