← previous blocknext block →recent activity

Analyzing

Block #71,448,283

22 transactions · 15 stateful · 2026-04-30 05:18:33 UTC

Parallelism

64/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,448,283  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xaa3f091a…aea5

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0000

0x116e7d…d8f1

4 touches
1 conflict

0x00000000…0001

0x116e7d…d8f1

4 touches
1 conflict

0x00000000…0003

0x116e7d…d8f1

4 touches
1 conflict

0x692a4122…76b8

0x350035…7777

4 touches
1 conflict

0xb7143610…adc4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0005

0x1397bd…f779

2 touches
0 conflicts

0xab2f6eed…254a

0x188d58…ea8e

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

28 conflicts on slot 0xaa3f091ad7…a2aea5

← previous block·next block →recent activity