← previous blocknext block →recent activity

Analyzing

Block #117,225,403

17 transactions · 16 stateful · 2026-10-28 04:00:28 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #117,225,403  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x42e917f7…ed8c

0x34b655…2a6f

4 touches
1 conflict

0xbcbd3c37…7f24

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x4c0627bd…f5c4

0x34b655…2a6f

4 touches
1 conflict

0xe1b6b3c8…6676

0x34b655…2a6f

4 touches
1 conflict

0x4c0627bd…f5c3

0x34b655…2a6f

4 touches
1 conflict

0x1112ec0d…623c

0x34b655…2a6f

3 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

1 conflict on slot 0x42e917f7fa…e0ed8c

← previous block·next block →recent activity