← previous blocknext block →recent activity

Analyzing

Block #102,436,519

16 transactions · 14 stateful · 2026-09-06 09:44:00 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,436,519  ·  16 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0xd53b61b7…311b

0x34b655…2a6f

6 touches
3 conflicts

0xbbc4bdf7…c62f

0x34b655…2a6f

6 touches
3 conflicts

0x581b829b…9578

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x8a79b23e…0d95

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity