← previous blocknext block →recent activity

Analyzing

Block #71,417,198

15 transactions · 14 stateful · 2026-04-30 01:51:26 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,417,198  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x676f9f01…a8ac

0x34b655…2a6f

12 touches
15 conflicts

0xa26089b8…812e

0x34b655…2a6f

8 touches
6 conflicts

0x21d22421…0b7a

0x34b655…2a6f

6 touches
3 conflicts

0x30c10c87…22ec

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x3b74ae43…a235

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

15 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity