← previous blocknext block →recent activity

Analyzing

Block #74,796,492

16 transactions · 15 stateful · 2026-05-15 17:29:05 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,796,492  ·  16 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

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0x319ab432…90a4

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x4002395e…ae61

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

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

6 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity