← previous blocknext block →recent activity

Analyzing

Block #102,056,626

15 transactions · 13 stateful · 2026-09-05 01:38:45 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,056,626  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x2e957c13…4777

0x34b655…2a6f

6 touches
3 conflicts

0x3a4aa25c…1e94

0x34b655…2a6f

4 touches
1 conflict

0x3d13406e…eff1

0x34b655…2a6f

4 touches
1 conflict

0x477cb4f5…11b4

0x34b655…2a6f

4 touches
1 conflict

0x4dffc33e…068d

0x34b655…2a6f

4 touches
1 conflict

0x898a08aa…c855

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xa2c04336…e4c0

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 0x2e957c1333…574777

← previous block·next block →recent activity