← previous blocknext block →recent activity

Analyzing

Block #102,484,267

19 transactions · 16 stateful · 2026-09-06 13:45:55 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,484,267  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…641f

0x34b655…2a6f

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0xa157099e…f1c3

0x34b655…2a6f

4 touches
1 conflict

0xa157099e…f1c4

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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 0xc824469a90…af641f

← previous block·next block →recent activity