← previous blocknext block →recent activity

Analyzing

Block #87,292,090

22 transactions · 16 stateful · 2026-07-12 15:00:33 UTC

Parallelism

77/100

Blocked

56%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,292,090  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x6f5435af…138b

0x34b655…2a6f

4 touches
1 conflict

0x71658d1a…f1ec

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

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: 0xb1dbf05f…b1c0d3

3 conflicts on slot 0x8a35acfbc1…6bd1aa

← previous block·next block →recent activity