← previous blocknext block →recent activity

Analyzing

Block #104,870,533

20 transactions · 20 stateful · 2026-09-14 22:49:58 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,870,533  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7c68d10b…8386

0x34b655…2a6f

12 touches
15 conflicts

0x02dab2c8…5cb1

0x34b655…2a6f

8 touches
6 conflicts

0xb5924647…4cf1

0x34b655…2a6f

8 touches
6 conflicts

0x29f17d49…e19b

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x711ceb8d…5202

0x34b655…2a6f

4 touches
1 conflict

0x81d64349…50fe

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 0x7c68d10b83…628386

← previous block·next block →recent activity