← previous blocknext block →recent activity

Analyzing

Block #74,331,764

32 transactions · 22 stateful · 2026-05-13 13:44:37 UTC

Parallelism

59/100

Blocked

73%

Avg conflicts / tx

2.69

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,331,764  ·  32 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xfec0a350…7ed2

0xd32edf…ff58

25 touches
78 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0003

0x116e7d…d8f1

6 touches
3 conflicts

0xbb12db23…857e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x116e7d…d8f1

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x692a4122…76b8

0x350035…7777

6 touches
3 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

78 conflicts on slot 0xfec0a350b9…fc7ed2

← previous block·next block →recent activity