← previous blocknext block →recent activity

Analyzing

Block #102,817,964

18 transactions · 17 stateful · 2026-09-07 17:53:30 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,817,964  ·  18 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

0x0d03bddb…6658

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x00000000…004f

0x80c745…7210

4 touches
1 conflict

0x4a39a2a4…857b

0x34b655…2a6f

4 touches
1 conflict

0x5a6c91e3…7d42

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xc824469a…6425

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 0x0d03bddb26…a56658

← previous block·next block →recent activity