← previous blocknext block →recent activity

Analyzing

Block #72,497,880

8 transactions · 6 stateful · 2026-05-05 01:59:08 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,497,880  ·  8 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

0xbfc2969c…3077

0x065c9d…c394

6 touches
3 conflicts

0xc25f30f4…1c93

0x065c9d…c394

4 touches
2 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x3426b99a…8012

0x065c9d…c394

3 touches
1 conflict

0x5db1ecb7…490f

0x065c9d…c394

2 touches
0 conflicts

0x936fdcd7…a0c1

0x065c9d…c394

2 touches
0 conflicts

0xfe635b81…c871

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity