← previous blocknext block →recent activity

Analyzing

Block #74,419,213

11 transactions · 10 stateful · 2026-05-13 23:26:31 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,419,213  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x116a621e…f97f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc08384da…ecb7

0x34b655…2a6f

6 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0x67d1be…196f

4 touches
1 conflict

0x2b936aa5…05e5

0x141b1d…9583

4 touches
1 conflict

0x00000000…0003

0x2ae0cf…3d4e

4 touches
1 conflict

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

3 conflicts on slot 0x116a621eee…adf97f

← previous block·next block →recent activity