← previous blocknext block →recent activity

Analyzing

Block #74,344,556

27 transactions · 13 stateful · 2026-05-13 15:09:41 UTC

Parallelism

63/100

Blocked

69%

Avg conflicts / tx

1.67

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,344,556  ·  27 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

0x09512428…de68

0xd32edf…ff58

19 touches
45 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0xb535b5ab…bd1b

0x0555e3…2b9c

2 touches
0 conflicts

0x00000000…0000

0x094452…0a09

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

45 conflicts on slot 0x09512428a3…18de68

← previous block·next block →recent activity