← previous blocknext block →recent activity

Analyzing

Block #71,070,793

17 transactions · 15 stateful · 2026-04-28 11:24:11 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,070,793  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x131a2e…0da9

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7f593fea…5f61

0x98dc6e…8633

2 touches
0 conflicts

0x66a083b4…a17a

0x065c9d…c394

2 touches
0 conflicts

0xcd621226…2df8

0x98dc6e…8633

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: 0xb857c13a…1a9be1

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity