← previous blocknext block →recent activity

Analyzing

Block #87,727,010

19 transactions · 19 stateful · 2026-07-14 15:30:00 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,727,010  ·  19 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

0x08803a9b…dfbd

0x34b655…2a6f

6 touches
3 conflicts

0xc4de6652…13f4

0x34b655…2a6f

6 touches
3 conflicts

0x1110ff7d…d969

0x34b655…2a6f

4 touches
1 conflict

0x1bbca09e…f873

0x34b655…2a6f

4 touches
1 conflict

0x1c108975…4807

0x34b655…2a6f

4 touches
1 conflict

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x2c390858…b1ed

0x34b655…2a6f

4 touches
1 conflict

0x3b18ecc3…dc4f

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: Perpl

3 conflicts on slot 0x08803a9be3…d0dfbd

← previous block·next block →recent activity