Block #72,213,214

← previous blocknext block →recent activity

Analyzing

Block #72,213,214

10 transactions · 9 stateful · 2026-05-03 18:18:02 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,213,214  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…003d

0x065c9d…c394

6 touches
3 conflicts

0x0af0537b…5fbf

0x065c9d…c394

4 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

4 touches
1 conflict

0x740f7728…9e15

0x065c9d…c394

4 touches
1 conflict

0xbd8f012b…0932

0x065c9d…c394

3 touches
1 conflict

0x6f5202f3…a2f7

0x065c9d…c394

3 touches
1 conflict

0xd0b7528a…20e1

0x065c9d…c394

3 touches
1 conflict

0x6b3246ef…7fa8

0x065c9d…c394

3 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity