← previous blocknext block →recent activity

Analyzing

Block #72,498,647

20 transactions · 12 stateful · 2026-05-05 02:04:15 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,498,647  ·  20 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x50c2960c…5f37

0x34b655…2a6f

4 touches
1 conflict

0x6423fcab…a7c1

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x75de687e…97a4

0x34b655…2a6f

4 touches
1 conflict

0x7a771ded…3675

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity