← previous blocknext block →recent activity

Analyzing

Block #102,740,630

19 transactions · 19 stateful · 2026-09-07 11:21:14 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,740,630  ·  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

0x3d93ad2c…e747

0x34b655…2a6f

6 touches
3 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0x014e90b3…470f

0x34b655…2a6f

6 touches
3 conflicts

0x31cf2d8d…5de8

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x96ed54e2…04ed

0x34b655…2a6f

6 touches
3 conflicts

0xaba6578d…bd48

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

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 0x3d93ad2c39…a6e747

← previous block·next block →recent activity