← previous blocknext block →recent activity

Analyzing

Block #71,700,925

15 transactions · 12 stateful · 2026-05-01 09:24:30 UTC

Parallelism

60/100

Blocked

42%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,700,925  ·  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

0xd581d055…e0a8

0xd32edf…ff58

9 touches
10 conflicts

0xa4b9a3a4…0d76

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xfac61869…a55f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x65f190cd…7d29

0x065c9d…c394

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 0xd581d0553c…81e0a8

← previous block·next block →recent activity