← previous blocknext block →recent activity

Analyzing

Block #86,243,185

12 transactions · 11 stateful · 2026-07-07 18:08:03 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,243,185  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x065c9d…c394

4 touches
1 conflict

0x0022e2fa…2641

0x34b655…2a6f

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x11431f9d…42c5

0x34b655…2a6f

4 touches
1 conflict

0x47f15132…8ec0

0x34b655…2a6f

4 touches
1 conflict

0x54a035dd…16c6

0x34b655…2a6f

4 touches
1 conflict

0x667658e1…e172

0x34b655…2a6f

4 touches
1 conflict

0x6f58168d…ea24

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: Kuru Exchange: Market-MON/USDC

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity