← previous blocknext block →recent activity

Analyzing

Block #74,403,499

26 transactions · 25 stateful · 2026-05-13 21:41:58 UTC

Parallelism

27/100

Blocked

72%

Avg conflicts / tx

6.58

Longest chain

19 deep

Execution timeline

did this block parallelize well?

view

block #74,403,499  ·  26 txs across 19 waves  ·  depth 19
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

wave w17

wave w18

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

0xaf7c2ffc…5a6f

0x3bd359…433a

38 touches
171 conflicts

0x00000000…0000

0xd004cf…da29

38 touches
171 conflicts

0x00000000…0001

0xd004cf…da29

38 touches
171 conflicts

0xdbde8233…3e76

0xdb8585…7777

38 touches
171 conflicts

0x00000000…0003

0xd004cf…da29

38 touches
171 conflicts

0x2d1ddb71…15ee

0xdb8585…7777

2 touches
0 conflicts

0x30d1accc…cb72

0xdb8585…7777

2 touches
0 conflicts

0x73a69d96…939d

0xdb8585…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

171 conflicts on slot 0xaf7c2ffc57…fb5a6f

← previous block·next block →recent activity