← previous blocknext block →recent activity

Analyzing

Block #87,715,066

19 transactions · 19 stateful · 2026-07-14 14:09:58 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,715,066  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6c0f0c32…94d7

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0x925dfa51…2cba

0x34b655…2a6f

4 touches
1 conflict

0xad2bb81f…4d6b

0x34b655…2a6f

4 touches
1 conflict

0xb56f0740…7542

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 0x6c0f0c32d4…fa94d7

← previous block·next block →recent activity