← previous blocknext block →recent activity

Analyzing

Block #86,566,638

26 transactions · 22 stateful · 2026-07-09 06:09:42 UTC

Parallelism

92/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,566,638  ·  26 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x342fbbca…d443

0x40c49f…2af0

4 touches
1 conflict

0x8a35acfb…d1a8

0xb1dbf0…c0d3

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb03a9929…85b3

0x065c9d…c394

4 touches
1 conflict

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x737acb78…fce8

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: 0x40c49f17…d22af0

1 conflict on slot 0x342fbbca09…fcd443

← previous block·next block →recent activity