← previous blocknext block →recent activity

Analyzing

Block #74,370,183

13 transactions · 10 stateful · 2026-05-13 18:00:07 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,370,183  ·  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

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3419a5c0…c708

0xd32edf…ff58

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0f4147f6…1599

0x065c9d…c394

2 touches
0 conflicts

0x6eee9f9e…2c25

0x065c9d…c394

2 touches
0 conflicts

0xa3b4bf7e…088d

0x065c9d…c394

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

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

1 conflict on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity