← previous blocknext block →recent activity

Analyzing

Block #72,284,212

20 transactions · 15 stateful · 2026-05-04 02:15:07 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,284,212  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xff1aa3b1…3466

0xd32edf…ff58

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x96e954c6…a9ef

0x065c9d…c394

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0xa980598e…ec52

0x3bd359…433a

2 touches
0 conflicts

0x81955a0a…29ee

0x6657d1…8ccc

2 touches
0 conflicts

0xafcbbaff…6afc

0x6657d1…8ccc

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: 0xd32edf66…9fff58

10 conflicts on slot 0xff1aa3b1e8…703466

← previous block·next block →recent activity