← previous blocknext block →recent activity

Analyzing

Block #72,370,643

8 transactions · 8 stateful · 2026-05-04 11:51:31 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,370,643  ·  8 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

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf6d214b0…8abe

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x976bb9a1…1d84

0x34b655…2a6f

4 touches
1 conflict

0xb1856468…e84f

0x34b655…2a6f

4 touches
1 conflict

0xc13a52e7…1fcd

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity