← previous blocknext block →recent activity

Analyzing

Block #71,648,418

29 transactions · 22 stateful · 2026-05-01 03:34:54 UTC

Parallelism

83/100

Blocked

50%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,648,418  ·  29 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

0xec6e3e10…bdb6

0xd32edf…ff58

9 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd77e90ec…8c04

0x3bd359…433a

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

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

10 conflicts on slot 0xec6e3e108a…52bdb6

← previous block·next block →recent activity