← previous blocknext block →recent activity

Analyzing

Block #87,316,708

16 transactions · 16 stateful · 2026-07-12 17:45:07 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,316,708  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa112f315…1a92

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0363d65e…06d2

0x34b655…2a6f

4 touches
1 conflict

0x1e166a45…98a7

0x34b655…2a6f

4 touches
1 conflict

0x45ea7a97…bbb3

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xa112f315bf…001a92

← previous block·next block →recent activity