← previous blocknext block →recent activity

Analyzing

Block #74,266,484

14 transactions · 13 stateful · 2026-05-13 06:30:22 UTC

Parallelism

36/100

Blocked

62%

Avg conflicts / tx

2.57

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,266,484  ·  14 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x293e2f…13a7

18 touches
36 conflicts

0xc27346d4…90a3

0x9c82eb…cd90

18 touches
36 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x446d1cef…5d3b

0x293e2f…13a7

2 touches
0 conflicts

0x67f94928…03be

0x293e2f…13a7

2 touches
0 conflicts

0x733abcff…4207

0x293e2f…13a7

2 touches
0 conflicts

0x885c8828…6c38

0x293e2f…13a7

2 touches
0 conflicts

0xc0473b93…d05c

0x293e2f…13a7

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: 0x293e2f01…5113a7

36 conflicts on slot 0x0000000000…000036

← previous block·next block →recent activity