← previous blocknext block →recent activity

Analyzing

Block #72,036,871

21 transactions · 19 stateful · 2026-05-02 22:41:13 UTC

Parallelism

62/100

Blocked

37%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,036,871  ·  21 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

0x00000000…0002

0x7e9d3a…9fda

16 touches
28 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001b

0x1b6862…e19c

2 touches
0 conflicts

0x10b8d161…8791

0x754704…b603

2 touches
0 conflicts

0xd821cffd…3ff0

0x754704…b603

2 touches
0 conflicts

0x00000000…0008

0x86dbf0…eb2d

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: 0x7e9d3a8a…4f9fda

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity