← previous blocknext block →recent activity

Analyzing

Block #102,095,116

20 transactions · 17 stateful · 2026-09-05 04:54:02 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,095,116  ·  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

0x71b395d9…1697

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3bd7558f…4af6

0x34b655…2a6f

6 touches
3 conflicts

0x32e1d03e…68a7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6823c28e…594c

0x34b655…2a6f

4 touches
1 conflict

0x7c93b38a…9e69

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

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 0x71b395d942…4d1697

← previous block·next block →recent activity