← previous blocknext block →recent activity

Analyzing

Block #74,588,475

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

Parallelism

45/100

Blocked

65%

Avg conflicts / tx

2.8

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,588,475  ·  20 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

0x86dfd5…6a7d

22 touches
55 conflicts

0x1686502b…a1d2

0x3bd359…433a

22 touches
55 conflicts

0x00000000…0000

0x86dfd5…6a7d

22 touches
55 conflicts

0x00000000…0002

0x86dfd5…6a7d

22 touches
55 conflicts

0x1d4c90ab…1ba7

0xb72e62…7777

22 touches
55 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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: 0x86dfd554…906a7d

55 conflicts on slot 0x0000000000…000003

← previous block·next block →recent activity