← previous blocknext block →recent activity

Analyzing

Block #86,288,453

20 transactions · 19 stateful · 2026-07-07 23:10:13 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,288,453  ·  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

0x00000000…0002

0x04fdea…47d7

14 touches
21 conflicts

0x00000000…0002

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0003

0x019883…2a9a

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x00000000…0000

0x019883…2a9a

6 touches
3 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: 0x04fdeac2…f747d7

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity