← previous blocknext block →recent activity

Analyzing

Block #72,100,137

17 transactions · 13 stateful · 2026-05-03 05:42:21 UTC

Parallelism

65/100

Blocked

46%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,100,137  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

2 touches
0 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x1c913164…5c2e

0x34b655…2a6f

2 touches
0 conflicts

0x220f4f84…15f8

0x34b655…2a6f

2 touches
0 conflicts

0x32ee90db…decc

0x34b655…2a6f

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

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity