← previous blocknext block →recent activity

Analyzing

Block #74,587,209

19 transactions · 17 stateful · 2026-05-14 18:11:17 UTC

Parallelism

63/100

Blocked

35%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,587,209  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x74c90b00…73c2

0x065c9d…c394

2 touches
0 conflicts

0xd3c6265d…c6f6

0x065c9d…c394

2 touches
0 conflicts

0xd8efca0e…8ee2

0x065c9d…c394

2 touches
0 conflicts

0xda10dfc3…0f35

0x065c9d…c394

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity