← previous blocknext block →recent activity

Analyzing

Block #87,504,112

20 transactions · 16 stateful · 2026-07-13 14:38:24 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,504,112  ·  20 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

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0xffa7d0a4…b10a

0x40c49f…2af0

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x9e49f754…23a2

0x34b655…2a6f

6 touches
3 conflicts

0x342fbbca…d443

0x40c49f…2af0

6 touches
3 conflicts

0x6b5ffec9…7c66

0x40c49f…2af0

4 touches
2 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xab774675…75f7

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity