← previous blocknext block →recent activity

Analyzing

Block #87,362,056

23 transactions · 18 stateful · 2026-07-12 22:48:21 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,362,056  ·  23 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

0xe90b7bce…c2e0

0xfa32f9…f3f0

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xfa32f9…f3f0

4 touches
1 conflict

0x00000000…0001

0xfa32f9…f3f0

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x139cf1a2…a1df

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: 0xfa32f9ec…fef3f0

1 conflict on slot 0xe90b7bceb6…a7c2e0

← previous block·next block →recent activity