← previous blocknext block →recent activity

Analyzing

Block #102,110,358

20 transactions · 19 stateful · 2026-09-05 06:11:20 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,110,358  ·  20 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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

6 touches
3 conflicts

0x64275949…d698

0x34b655…2a6f

6 touches
3 conflicts

0x6db1a1a0…e820

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xa0dc2aef…ea3e

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity