← previous blocknext block →recent activity

Analyzing

Block #72,296,687

20 transactions · 17 stateful · 2026-05-04 03:38:53 UTC

Parallelism

65/100

Blocked

41%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,296,687  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc13c1093…9a9d

0x754704…b603

10 touches
10 conflicts

0xc1ceff4b…04a0

0x3bd359…433a

10 touches
10 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x7e28e55c…d05c

0x754704…b603

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

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: 0x754704bc…afb603

10 conflicts on slot 0xc13c10937b…749a9d

← previous block·next block →recent activity