← previous blocknext block →recent activity

Analyzing

Block #72,036,936

16 transactions · 12 stateful · 2026-05-02 22:41:39 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,036,936  ·  16 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x0d6fb43d…d264

0x34b655…2a6f

2 touches
0 conflicts

0xac2a0273…7212

0x34b655…2a6f

2 touches
0 conflicts

0xf853eb8e…401e

0x34b655…2a6f

2 touches
0 conflicts

0x536e2740…61ac

0x3bd359…433a

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity