← previous blocknext block →recent activity

Analyzing

Block #102,215,555

20 transactions · 20 stateful · 2026-09-05 15:04:32 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,215,555  ·  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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x2e21046b…5e16

0x34b655…2a6f

6 touches
3 conflicts

0x0005a008…264a

0x34b655…2a6f

6 touches
3 conflicts

0x044844a0…7418

0x34b655…2a6f

6 touches
3 conflicts

0xaa072b82…3dde

0x34b655…2a6f

4 touches
1 conflict

0x8ec95f2b…f4d7

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity