← previous blocknext block →recent activity

Analyzing

Block #74,392,493

9 transactions · 7 stateful · 2026-05-13 20:28:39 UTC

Parallelism

56/100

Blocked

43%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,392,493  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

4 touches
1 conflict

0x77100a2a…91a4

0x34b655…2a6f

4 touches
1 conflict

0xb593de77…e4fe

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

2 touches
0 conflicts

0xb245fe36…d765

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity