← previous blocknext block →recent activity

Analyzing

Block #100,874,659

20 transactions · 19 stateful · 2026-08-31 22:25:44 UTC

Parallelism

75/100

Blocked

32%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,874,659  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x74e485b1…d380

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x06e40499…165e

0x34ae4d…3fc5

4 touches
1 conflict

0xa605468c…1bfc

0x34ae4d…3fc5

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x44eb85cc…94c0

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

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 0x74e485b13a…f0d380

← previous block·next block →recent activity