← previous blocknext block →recent activity

Analyzing

Block #74,210,252

22 transactions · 13 stateful · 2026-05-13 00:16:29 UTC

Parallelism

55/100

Blocked

69%

Avg conflicts / tx

2.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,210,252  ·  22 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

0x2f283cf0…36fb

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x65bd5770…5ed1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x692a4122…76b8

0x350035…7777

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: 0xd32edf66…9fff58

45 conflicts on slot 0x2f283cf08e…f136fb

← previous block·next block →recent activity