← previous blocknext block →recent activity

Analyzing

Block #74,344,485

25 transactions · 23 stateful · 2026-05-13 15:09:13 UTC

Parallelism

32/100

Blocked

74%

Avg conflicts / tx

5.48

Longest chain

17 deep

Execution timeline

did this block parallelize well?

view

block #74,344,485  ·  25 txs across 17 waves  ·  depth 17
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

wave w13

wave w14

wave w15

wave w16

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

0xb4b3c404…f0aa

0x3bd359…433a

34 touches
136 conflicts

0x00000000…0000

0x579d00…83f8

34 touches
136 conflicts

0x00000000…0002

0x579d00…83f8

34 touches
136 conflicts

0x00000000…0003

0x579d00…83f8

34 touches
136 conflicts

0x399cd013…b14f

0x23ae8c…7777

34 touches
136 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x937d187e…e650

0x23ae8c…7777

2 touches
0 conflicts

0x94ac3947…9d9f

0x23ae8c…7777

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: 0x3bd359c1…15433a

136 conflicts on slot 0xb4b3c404bb…77f0aa

← previous block·next block →recent activity