← previous blocknext block →recent activity

Analyzing

Block #74,325,544

23 transactions · 23 stateful · 2026-05-13 13:03:18 UTC

Parallelism

52/100

Blocked

57%

Avg conflicts / tx

2.65

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,325,544  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd5bf41…8148

22 touches
55 conflicts

0x2d5f4089…4e8a

0x3bd359…433a

22 touches
55 conflicts

0xd50086ec…092b

0xd7c1ef…7777

22 touches
55 conflicts

0x00000000…0000

0xd5bf41…8148

22 touches
55 conflicts

0x00000000…0001

0xd5bf41…8148

22 touches
55 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0xa10c86f8…4b74

0x3bd359…433a

8 touches
6 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: 0xd5bf41b2…238148

55 conflicts on slot 0x0000000000…000003

← previous block·next block →recent activity