← previous blocknext block →recent activity

Analyzing

Block #74,409,862

13 transactions · 9 stateful · 2026-05-13 22:24:22 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,409,862  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x94710b77…a921

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x10a191e0…3056

0x34b655…2a6f

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x3fda6d00…7426

0x5afd3e…7620

2 touches
0 conflicts

0xdb558e72…fe29

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0006

0x60bb42…87ea

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: Perpl

1 conflict on slot 0x6f6fc26c68…133e34

← previous block·next block →recent activity